Add support for DeviceAuthURL and a Provider.Config() API #140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The go-oidc library added support for
DeviceAuthURL
in coreos/go-oidc#365. This adds it also to the cap library and also makes aProviderConfig
structure available through a new API callProvider.Config()
so an application like the one added in hashicorp/vault-plugin-auth-jwt#131 that needs those URLs does not need to discover them itself. Note that it does not include JWKSURL because that is not available through the go-oidc API.At the same time, this adds
DeviceAuthURL
to theDiscoveryInfo
API.