Skip to content
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

OIDC Azure provider - There are no any groups in response #1081

Closed
vutkin opened this issue Aug 23, 2022 · 3 comments
Closed

OIDC Azure provider - There are no any groups in response #1081

vutkin opened this issue Aug 23, 2022 · 3 comments

Comments

@vutkin
Copy link

vutkin commented Aug 23, 2022

Expected Behavior

If some user in Azure AD has 150+ groups in response (included subgroups) there will be no any groups, and Azure expects that application will do a second separate request to GraphQL request for groups only.

Like dex do for ex. https://dexidp.io/docs/connectors/microsoft/

Actual Behaviour

Works well when number of Azure AD groups for user is less than JWT/SAML limit

Steps To Reproduce

image

Ref: https://docs.microsoft.com/en-gb/azure/active-directory/hybrid/how-to-connect-fed-group-claims

Example:

DEBUG in application: Body: {"providerType":"OIDC","providerName":"azuread","username":"[email protected]"}

Environment Information

JDK: openjdk-11
OS: registry.access.redhat.com/ubi8/openjdk-11:1.13

Example Application

https://github.com/tchiotludo/akhq

Version

0.21.0

@vutkin
Copy link
Author

vutkin commented Nov 28, 2022

Any update?

@sdelamo
Copy link
Contributor

sdelamo commented Dec 20, 2022

@vutkin I think you are going to need to provide a replacement and do this extra request.

@vutkin
Copy link
Author

vutkin commented Sep 20, 2023

Switched to DEX IDP.

@vutkin vutkin closed this as completed Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants