go-oidc VS pflag

I use the following code with this lib

If oidc supported, check out https://github.com/coreos/go-oidc You can instantiate a oidc verifier by passing the oidc-configuration endpoint, set the remote public key set by passing the jwks endpoint. Then call Verify func. As long as the public key matches the private key used to sign the JWT (3rd part), you'll verify it and get the claim back, then unmarshall that claim to some struct and you're good to go.

This looks so far like some of the nicest ones. I'm sold if you add the possibility for OpenID connect authentication that can be configured via env variables to the container.

I did everything according to go-oidc examples: https://github.com/coreos/go-oidc/blob/v3/example/idtoken/app.go

go-oidc: github.com/coreos/go-oidc

If you actually have OpenID Connect then there are some good libraries to use for token management in that case. Iirc I prefer https://github.com/coreos/go-oidc, since it supports auto discovery and key rotation etc.

oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).

Hmm, this might be a relevant issue: https://github.com/golang/oauth2/issues/128 . On the face of it, it looks like https://github.com/coreos/go-oidc is a more thorough implementation...(?)

My understanding is that you can use pflag as a drop in replacement of the standard lib's flag (import flag "github.com/spf13/pflag"). So it can be used as a standalone lib I suppose.

I realy enjoyed the patched version from spf13 with "--" support https://github.com/spf13/pflag

Nice, but Cobra (with pflag underneath) is so, so better.

Not by default on stdlib. There are libraries available though - https://github.com/spf13/pflag

Flag functionality is provided by the pflag library, a fork of the flag standard library which maintains the same interface while adding POSIX compliance.

How does it compare to https://github.com/spf13/pflag ?

spf13 has a drop in pflag that does the - short and -- long flags.

oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).

What are the benefits of this package over the widely used spf13/pflag?

3