Proposal to add -provider and --provider-list options to simplify endpoint config

[tonymet]

Thanks for the great tool . I appreciate the automatic endpoint configuration using .well-known/. We could further improve usability by adding a provider option e.g. oauth2c --provider microsoft or --provider google . Provider would load the endpoint configuration from Endpoint defintions found in the go module https://pkg.go.dev/golang.org/x/oauth2#section-directories .

Moreover , it would be a great contributor opportunity to add the full gamut of oauth providers .

If there's interest, I'm happy to start the initial PR

Example Run

Perform oauth code-based authentication using microsoft

> oauth2c --provider microsoft --client-id xxxx-xxxx --client-secret yyyyyy.yyy --scopes ...

List Available Providers

> oauth2c --provider-list
 Oauth2c provides endpoint configuration for the following providers:
facebook
google
instagram
microsoft
github
gitlab
fitbit
foursquare
heroku
hipchat
jira
kakao
linkedin
mailchimp
mailru
mediamath
nokiahealth
odnoklassniki
paypal
slack
spotify
stackoverflow
twitch
uber
vk
yahoo
yandex

[ikawalec]

Hi @tonymet

That sounds like a great idea! Feel free to create a draft PR.

Thanks!

[saper]

But for Microsoft, do we want v1.0 or v2.0, or both? I've run into big differences in behaviour of these.

(In theory, OIDC metadata should solve this problem)

[tonymet]

But for Microsoft, do we want v1.0 or v2.0, or both? I've run into big differences in behaviour of these.

(In theory, OIDC metadata should solve this problem)

i was leaning toward 2.0, but if you help with the naming, adding both would be possible.

thanks for engaging on this it had slipped a bit when I ran into some integrations challenges. i'll give it another go