-
Notifications
You must be signed in to change notification settings - Fork 68
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
How to configure Guild Checking? #24
Comments
Also having this issue! |
Sorry for the late response. It can be configured by setting I will try to implement the new admin console support. Thanks for the feedback! |
Unfortunately, even the latest Keycloak v20 does not support custom provider settings in the new admin console. We need to wait first for the new admin console side to be fixed. |
Thanks for following up @wadahiro, I appreciate it! I will keep an eye on keycloak/keycloak#17958 also |
Although keycloak/keycloak#17958 was closed, now the issue is discussed in keycloak/keycloak#15344. |
I notice both of the linked issues are now closed. I've been unable to get version 21.1.2 to startup with the suggested them or admin2 disables. The theme causes an internal error and disabling admin2 seems to just turn admin off all together. Is this now possible with the above issues closed or is there any way I can manually configure this even without display in the UI? I'm running the bitnami chart if that matters at all. |
I confirmed the problem was resolved by the following pull requests:
I created a pull request for support keycloak 22 and the new admin console: #37 |
🎉 This issue has been resolved in version 0.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
From what I understand from the README it appears there is an option for only allowing members of certain guilds to log in into Keycloak using this Provider.
However, I can't find the option to specify the guilds allowed:
Could you please point me in the right direction on where I can configure this feature?
Thank you!
The text was updated successfully, but these errors were encountered: