We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently we pass the jwks URL directly to the backend via the config
this is not standard - instead giving the OIDC discovery URL would be more standard, where the backend automatically finds the jwks url
The text was updated successfully, but these errors were encountered:
https://pkg.go.dev/github.com/pardot/oidc/discovery#NewClient
We can carry out OIDC discovery using this library
Sorry, something went wrong.
Modify JWKS URL in config to Issuer URL for OIDC Discovery in Backend (…
f762363
…#370) (#393) * Modify JWKS URL in config to Issuer URL for OIDC Discovery in Backend Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com> * Update tests Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com> * Lint fixes Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com> * remove accidental swp file Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com> * added documentation Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com> --------- Signed-off-by: Maia Iyer <maia.raj.iyer@gmail.com>
maia-iyer
Successfully merging a pull request may close this issue.
Currently we pass the jwks URL directly to the backend via the config
this is not standard - instead giving the OIDC discovery URL would be more standard, where the backend automatically finds the jwks url
The text was updated successfully, but these errors were encountered: