-
Notifications
You must be signed in to change notification settings - Fork 548
binding user account with email #2085
Comments
@yqwang-ms , can we allow "-" and "@" in the user name? |
|
For what we allowed, please check: |
can we rewrite "@" in the user name to "#"when using it in a uri way? Or maybe we should differentiate "user id" from "user name": the current user name should actually be user id. and we can introduce another field called "user alias" or "email". |
But # is also not allowed in URI, URI only allows below, may be we need another one. For k8s launcher, I keep align with Statefulset who uses -, it is more complex thing we can disscus later given k8s has more strong naming convention on object name, label name, env name. |
If it just an URI issue, we could encode them. |
Agree 👍 |
@Gerhut and @yqwang-ms , with the support of AAD, we should be able to support "-" or "." in user name. This is a must-have now. |
"-" or "." is already allowed in YARN Launcher. |
@yqwang-ms - what else is needed besides YARN Launcher supports? |
I am not sure, @Gerhut may know the details. |
rest server has some constraint. @Gerhut and @wangcan0329 have more information. |
cc @xiaowuhu for reference. |
It seemed the full email address as user name should be supported when we enable Open ID login. From here https://en.wikipedia.org/wiki/Email_address#Local-part we can see a more versatile email address format, so I think our rules might need to be updated. |
Thanks @sterowang , seems need to mark this one as higher priority to unblock Open ID login. |
Currently, user account can not contain "-" and "@", user does not have email address info.
To maintain users email, I have to maintain a table to keep the alias. And some users who start with "v-" cannot have the same user account as their alias.
The text was updated successfully, but these errors were encountered: