Hello all, does anyone encounter this kind of error? After enable an old user account I have this error
1 Like
Does the username have a . (period) or _ (underscore) in it?
2 Likes
Hey Chad, yes we all use email address as user with dot. that person was a rehire. so I just have to enable the account. but after enabling I have this issue
1 Like
There’s an undocumented change in 2024.2 and newer where a period or underscore in the username breaks authentication for the user. I’ve been going back and forth with support on this for going on 6 weeks.
Are you cloud or on-prem?
6 Likes
that sucks. yeah were on cloud
2 Likes
Nice
2 Likes
It does. And it only impacts new accounts and re-enabled accounts. If the account is enabled when the upgrade to 24.2+ happens it’s fine. But if you create a new user with a period or underscore or re-enable a user you run into issues. It also breaks authentication if you change the password for a user with a . or _ in the username.
6 Likes
I explicitly asked support for KB or some sort of product documentation that covers this change. They said that nothing exists but this is the new way it works. It’s a big deal for anyone who users periods or underscores in usernames. Both of which are very common characters in usernames.
5 Likes
then we have to wait for the 2026 version 
1 Like
Are you sure about this? I know we’ve been updating passwords on existing accounts without issue.
1 Like
More bad news there. They aren’t fixing it. This is a changed they made on purpose. You may have to open a support ticket. There’s a weird workaround where you can change a password and recycle the app server which allows login.
4 Likes
I was able to recreate the issue and support was. At least on 24.2 anyway. Support was able to recreate the issue in 24.2 and 25. But since they aren’t supporting . or _ anymore they weren’t going to open a problem for it.
5 Likes
I just created Testy.Testerson in my pilot environment… no issue.
Enabled… signed in… changed password… logged in again. No problems.
2 Likes
They should use AI which states that _ and . are safe to use in usernames, have very little security risk. I know many large corporations that use periods.
Maybe @Olga knows if this was made more due Linux containers or something.
2 Likes
Yeah we have some issues on expense entry but they say they already fixed it on the new version. and just have to wait till May 2026
2 Likes
Interesting they are fixing it. I was told it wasn’t being “fixed” and to just not use . or _.
3 Likes
So maybe support isn’t all on the same page. @Olga do you know anything about this?
3 Likes
I guess what they mean to say that they’ve already fixed it on version 2026 not 2025.2.7
1 Like
It looks like it. I will reply to support and see what they say. Those emails from support above were from earlier today.
2 Likes