-
Notifications
You must be signed in to change notification settings - Fork 6
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
Should username be editable? #464
Comments
Changing usernames is quite a can of worms. For example---if I change my username, does that mean someone else can then use my previous one or should it be blocked for some time. It can be done, but it isn't as simple as just changing an entry in the db---it'll require a lot more thought. This was also discussed in the Fedora community for their new auth system, so you can see the discussion here (they use IPA as their backend etc. but the general issues are the same): |
Should we disallow username change? |
Probably the best thing to do for the moment. We can revisit this later if we get requests from users to change usernames? |
I'm for disallowing the change for now too as I don't really it as a feature worth supporting. As Padraig points out is not a relationship key so shouldn't be troublesome in general, but we may need to check some edge cases where the username may be cached in the frontend |
Agreed that username should be shown and be greyed out in the edit form. |
Was looking into this. The I looked at the cloudharness code, and it looks like an authentication_token is necessary for the user look up? If no token is provided, it returns |
feat(user-editor): disable username field (fixes #464)
Username not editable now |
In the Edit my profile dialog, you can change your username. Is this by design? I know the long keycloak id is the unique key, but is there anywhere else a changed username will cause issues?
The text was updated successfully, but these errors were encountered: