-
Notifications
You must be signed in to change notification settings - Fork 367
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
[Google] Full email needed in admin_users even if domain gets stripped via hosted_domain config #674
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
I found that this is just the case only for the admin accounts. For the normal users, it requires only |
There is a bugfix related to this in oauthenticator, as found in z2jh 3.0.2 released a day or two ago, what version of the chart did you install exactly? |
This bug relates to your config - what is your authenticator config? Do you have hosted_domain configured? The regression in oauthenticator related to a change for such config. |
Looks the helm chart is
As you said, I have |
Check the changelog of this chart, it links to the oauthenticator projects changelog |
Thanks @consideRatio ! I found this link from the changelog:
? or is it originally intended that the |
This comment was marked as duplicate.
This comment was marked as duplicate.
That is a bug! |
Bug description
When helm 2.0.0 with z2jh 3.x, Google OAuth2 works only with "username", not the full email address. However, after upgrading to helm 3.0.x with z2jh 4.0.x, it requires full email.
The problem is, when I change the username to its full email address, the login name is still truncated. In other words, when the user's email is
username@example.com
, the logged username will be just theusername
.This
username
will be used for the single user's pod name, volume claims and so on, as well as the admin page like this:When I start the server from the user
username@example.com
, it doesn't use any attached claims or volumes with just theusername
. If the actual user didn't login, the admin cannot handle the user's singleuser instance at all.Expected behaviour
Actual behaviour
How to reproduce
Your personal set up
The text was updated successfully, but these errors were encountered: