go-oidc VS urfave/cli

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...(?)

Can you use a framework like urfavecli https://github.com/urfave/cli? This will auto-update every time it detects a new version from your CLI's GitHub repository

I use https://github.com/urfave/cli for local development over cli parameter inside docker over envs

....\Softwares\go\src\prysm\cmd\prysmctl\checkpointsync\cmd.go:3:8: cannot find package "github.com/urfave/cli/v2" in any of:

urfave/cli - A simple, fast, and fun package for building command line apps in Go;

and probably something else will be added in the future. The final kind of launch command would like to see such djob [options] - command. Command is the command (with arguments to run). -- should separate the arguments of the utility from the arguments of the program to run. There are several excellent solutions for working with command-line arguments, such as spf13/cobra or urfave/cli. But they’re good for building an interface out of a lot of commands, and for one (as in my example) they’re redundant. So I used the flag library. I have defined the following structure with arguments:

There are alternatives available for Cobra as well i.e. mitchellh/cli, go-flags, urfave/cli etc.

https://github.com/urfave/cli - A Golang package used to structure the CLI.