You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
I am not looking for support or already pursued the available support channels without success.
Version
2.37.0
Storage Type
Kubernetes
Installation Type
Official Helm chart
Expected Behavior
Logging into Dex with Microsoft as backend connector transforms the camelcase email from Microsoft AD correctly into a lowercase email. When the access token expires and a new one is issued using the refresh token, the email address should be transformed again.
After refreshing the access token, Kubernetes API-Server doesn't authorize the token since the email doesn't match the RoleBinding anymore.
Actual Behavior
When the access token expires and a new one is issued using the refresh token, the email address is not transformed again.
Steps To Reproduce
No response
Additional Information
No response
Configuration
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
hur
added a commit
to hur/dex
that referenced
this issue
Aug 16, 2024
Preflight Checklist
Version
2.37.0
Storage Type
Kubernetes
Installation Type
Official Helm chart
Expected Behavior
Logging into Dex with Microsoft as backend connector transforms the camelcase email from Microsoft AD correctly into a lowercase email. When the access token expires and a new one is issued using the refresh token, the email address should be transformed again.
After refreshing the access token, Kubernetes API-Server doesn't authorize the token since the email doesn't match the RoleBinding anymore.
Actual Behavior
When the access token expires and a new one is issued using the refresh token, the email address is not transformed again.
Steps To Reproduce
No response
Additional Information
No response
Configuration
No response
Logs
No response
The text was updated successfully, but these errors were encountered: