[BUG]: 2 lettered usernames & SSO

[jabsammy]

Describe the bug

Hello! Loving the new release :)

I noticed a small thing: my sso-user has a 2 lettered username and when auto-registering in jotty, i get my 2 lettered username. In the user setting, when trying to give my user a password, i get an error like this:

I suggest easing the username constrains and allowing for 2 letter usernames as they are quite common in private selfhosted deployments :)

Steps to Reproduce

• autoregister a SSO-jotty user with a 2 lettered prefered_username
• go into user settings and try to set a new passwort for said user

How do you run Jotty?

Docker

Jotty Version

latest

Checklist

• I have searched across other issues to make sure this bug has not been already reported.

[fccview]

Oh hi!
That's valid, I can do that for next release, sorry you just missed today's one 😆

I'll sort it out for you. That's definitely whats causing the error yeah?

[jabsammy]

Yes, this is definitely the issue. Using my testuser-sso account with more letters, i can change the password in the admin interface without problems.

Another thing that still remains is the fact that sso-registered users cannot change their passwort themselves since no password yet exists. This also prohibits users from deleting their account since no passwort is set. Do you want me to create an issue for that?

[jabsammy]

I just realized that when setting up jotty for the first time, you can set a 2 lettered username. Only in the password-changing menu, usernames with 2 letters are prohibited!

[fccview]

I just realized that when setting up jotty for the first time, you can set a 2 lettered username. Only in the password-changing menu, usernames with 2 letters are prohibited!

That sounds about right, I did remember reducing the amount of characters for user reg, but I wasn't sure.
Thank you for going in and trying to debug this for me, I'll sort it all out.

And yeah the sso users not being able to change their own password is a big issue, definitely gonna sort it out as part of this bug ticket ❤️