-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
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
Missing env variable in OIDC configurations that require issuer #11802
Comments
This is not unique to Keycloak. See my comment: #11848 (comment) Essentially, any self-hosted/instantiated OIDC provider needs this. |
This issue was marked with the This means that it is a good candidate for someone interested in contributing to the project, but does not know where to start. Have a look at the Contributing Guide first. This will help you set up your development environment to get started. When you are ready, open a PR, and link back to this issue in the form of adding Please make sure that - if applicable - you add tests for the changes you make. If you have any questions, feel free to ask in the comments below or the PR. Generally, you don't need to Note There is no need to ask for permission "can I work on this?" Please, go ahead if there is no linked PR 🙂 |
@balazsorban44 I went through the provider documentation pages and listed the ones requiring These are the ones I found:
I added a field to the Please let me know if I missed any providers or wrongly included any of them. Also, please review my PR #11976 . Thanks! |
What is the improvement or update you wish to see?
When following the getting started guide and selecting keycloak, there is no mention of the "AUTH_KEYCLOAK_ISSUER" variable
It will result in the following error "[auth][error] InvalidEndpoints: Provider "keycloak" is missing both
issuer
andauthorization
endpoint config."The information is correct in the dedicated keycloak page
Is there any context that might help us understand?
none
Does the docs page already exist? Please link to it.
No response
The text was updated successfully, but these errors were encountered: