-
-
Notifications
You must be signed in to change notification settings - Fork 692
Oauth 2, support role as string or array #840
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
Comments
Does look suprinsing so far. |
login succed: redirects to akhq topics, login fails : stays on login screen |
no error on backend log ? |
no backend error so far, think stays on login screen because it is not mapping any group/role |
OK so must be catch by micronaut and I think I can't do anything for that ... |
whenever the group-field:roles comes as a individual string instead of an array, akhq redirects back to login screen always, when the group-field:roles comes as an array from oidc provider it works fine without issue, is there a way to support the string as well? |
I don't think it's possible, keep it open to look at in the future. |
thanks for taking some time to this |
Hi, whenever we try to login using pingf , if the user on pingf has only one role/group attached in oidc then it comes as a string instead of an array and akhq don't recognize that role/group, any advice on this ?
oidc clame retuns something like this, login fails
{
"client_id": "some_id",
"lastName": "some_last_name",
"firstName": "some_name ",
"roles": "some_role",
}
oidc clame retuns something like this, login succeeds
{
"client_id": "some_id",
"lastName": "some_last_name",
"firstName": "some_name ",
"roles": ["some_role","another_role"],
}
oidc config is like below
The text was updated successfully, but these errors were encountered: