Ory Hydra
zap
Ory Hydra | zap | |
---|---|---|
37 | 52 | |
15,167 | 21,113 | |
0.7% | 0.8% | |
9.1 | 8.1 | |
7 days ago | 5 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Ory Hydra
- Show HN: Open-source OAuth2 server Ory Hydra now 6x faster
-
🚀 Top 12 Open Source Auth Projects Every Developer Should Know 🔑
OAuth Server - Hydra
-
Ask HN: Freelancer? Seeking freelancer? (July 2023)
For examples of my work see my contributions to Ory Hydra https://github.com/ory/hydra.
I'd be more than happy to talk about how I can bring value to your project. Let's have a conversation!
- Show HN: Open-Source OAuth2/OIDC Server Ory Hydra 2.1.2 Release
- Open Source OAuth2/OIDC Server Ory Hydra v2.1.2 Released
-
Ory Hydra VS boruta-server - a user suggested alternative
2 projects | 22 May 2023
-
Are there any OIDC Provider libraries for Golang?
Another package you might want to consider is ORY Hydra. https://github.com/ory/hydra
-
Advice me user and oauth2
Check this project: https://github.com/ory/hydra
-
Show HN: Kinde – auth, feature flags and billing (Q3) in one integration
> 10k M2M tokens for $250/month sounds like a really bad deal if I can just spin up https://github.com/ory/hydra that can easily handle 10k requests per second.
Spinning one up is easy, sure. Making sure it's production ready, is not so much.
-
Tailscale – Introducing Custom OIDC
Have not tried Dex so can't speak to that.
https://github.com/ory/hydra
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
What are some alternatives?
casdoor - An open-source UI-first Identity and Access Management (IAM) / Single-Sign-On (SSO) platform with web UI supporting OAuth 2.0, OIDC, SAML, CAS, LDAP, SCIM, WebAuthn, TOTP, MFA and RADIUS [Moved to: https://github.com/casdoor/casdoor]
logrus - Structured, pluggable logging for Go.
IdentityServer - The most flexible and standards-compliant OpenID Connect and OAuth 2.x framework for ASP.NET Core
zerolog - Zero Allocation JSON Logger
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
slog
dex - OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors
glog - Leveled execution logs for Go
Ory Kratos - Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!
go-log - a golang log lib supports level and multi handlers
node-oidc-provider - OpenID Certified™ OAuth 2.0 Authorization Server implementation for Node.js
log - Structured logging package for Go.