jwx VS oidc

I made a custom OIDC provider for integ tests using https://github.com/lestrrat-go/jwx, and a server than served out a .well-known/openid-configuration file and a jwks.json referenced by the openid-configuration.

Out of github.com/lestrrat-go/jwx, I only use the jwk part. It's been a month or so that I did that part, I don't recall what was the challenge either way. Time to review...

Check this lib: https://github.com/lestrrat-go/jwx

IMHO, lestrrat-go/jwx is the best JOSE (that means "JWS/JWE/JWK/JWA/JWT") library for Go. If you're using JWT I recommend using jwx. The last time I looked at golang-jwt/jwt it ignored most of JOSE. lestrrat-go/jwxis better written comprehensive.

Can I, similar to this code snippet, use context.Background() but in production code:

...then that's the JWT. You need to decode it using a JWT library. I suggest github.com/lestrrat-go/jwx.

Zitadel OIDC library code is very well-writen and informative.

Highly encourage everyone jump into source code and explore how IntrospectionResponse struct work with all related code around

https://github.com/zitadel/oidc/blob/main/pkg/oidc/introspec...

// IntrospectionResponse implements RFC 7662, section 2.2 and

// OpenID Connect Core 1.0, section 5.1 (UserInfo).

// https://www.rfc-editor.org/rfc/rfc7662.html#section-2.2.

// https://openid.net/specs/openid-connect-core-1_0.html#Standa....

type IntrospectionResponse struct {

I started with https://github.com/zitadel/oidc/tree/main/example/server/storage

oidc: github.com/zitadel/oidc (certified by OIDC)

I had to set up a OIDC server so our website could act as OIDC provider, and was really surprised how hard that is to do if you simply need the most basic setup. In fact it would seem that everybody would just keep a Keycloak or whatever— in their cluster and would keep it up-to-date with whatever user schema they would have in their app. This felt like too much work for me (I didn't want to maintain a whole extra service to just be able and provide a couple Oauth scopes from our API back-end.) so instead I went on and implemented the server directly in our app using https://github.com/zitadel/oidc. In fact this was the only fully-functioning OIDC implementation in Go that I could just plug in and make it work. So big props up to the Zitadel guys, the only worry would be from my side that the server implementation could be more generic and could rely on a set of interfaces that the users would be able to implement easily, without having to import a bunch of code from 'examples/server' like we have to do at the moment?

I just wanted to spread the word, that we moved the library to a new home in the ZITADEL GitHub organisation to ease some of the confusion around the name of the company (CAOS) and the project (ZITADEL).

But to ease the pain of this we release personal access tokens in March and are currently prepping to support client credentials as well, thanks to a contribution.