-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support for "direct grant" authentication flow #82
Comments
Hi, |
Unfortunately, restarting keycloak didn't fix the problem. Is there something else we might miss? |
I'm sorry, i did not read your initial text properly. This provider is meant for browser authentication and not for direct grant. |
Could this be implemented in a future release? |
it sure could, but it is currently not planned. I'm also not familiar with the "direct grant" flow, so i can not estimate how much work it would be. If you could give some insight, that would be great. |
Our development team is developing an app which authenticates via KeyCloak using the direct access grant flow. A request sent by the app looks something like this:
This should return an access token. Do you generally also offer support for custom features, similar to the main project PrivacyIDEA? |
Thanks for the info. It should be possible to make that work with our provider.
Yes we do |
+1 |
Hi,
I try to configure a "direct grant" authentication flow and adapting this guide. However, I get the error message "path was null". Am I missing something or is this feature not implemented (yet)?
Authentication Flow:
Error message:
The text was updated successfully, but these errors were encountered: