RomM version
4.8.1 (docker)
Describe the bug
All my usernames have a . in them. ROMM doens't allow usernames with a . in them, but if a username is supplied via OIDC with a . in it then the account will be created.
However you cannot edit the account settings (such as promoting the user to an admin) unless you first rename the account to remove the .
To Reproduce
Steps to reproduce the behavior:
- Configure ROMM to use OIDC
- Use OIDC to login to ROMM with an account with a username that features a
. in it
- Login using a different admin account
- Attempt to edit the account created in step 2.
Expected behavior
Personally I don't see the issue with allowing usernames with a . in them. However if you want to keep banning them, then either the OIDC login should fail, or the . should be replaced with an allowed character, such as a -
Screenshots
If applicable, add screenshots to help explain your problem.
Server (please complete the following information):
- OS: Debian 13 LXC running on proxmox. ROMM is running as a docker container
Client (please complete the following information):
- Device: Laptop
- OS: Ubuntu 24.04.4 LTS
- Browser Chrome
- Version Version 147.0.7727.116 (Official Build) (64-bit)
RomM version
4.8.1 (docker)
Describe the bug
All my usernames have a
.in them. ROMM doens't allow usernames with a.in them, but if a username is supplied via OIDC with a.in it then the account will be created.However you cannot edit the account settings (such as promoting the user to an admin) unless you first rename the account to remove the
.To Reproduce
Steps to reproduce the behavior:
.in itExpected behavior
Personally I don't see the issue with allowing usernames with a
.in them. However if you want to keep banning them, then either the OIDC login should fail, or the.should be replaced with an allowed character, such as a-Screenshots
If applicable, add screenshots to help explain your problem.
Server (please complete the following information):
Client (please complete the following information):