Home Assistant auth provider is running in legacy mode because we detected usernames that are case-insensitive equivalent.

[Bastian007]

The problem

Since 2022.12 I receive the following Log Message:

Logger: homeassistant.auth.providers.homeassistant
Source: auth/providers/homeassistant.py:326

Home Assistant auth provider is running in legacy mode because we detected usernames that are case-insensitiveequivalent. Please change the username: 'mareike'.

The username doesn't contain capitals. So the message is not fully clear. I also noticed the message was not given with 2022.11.

Please find here the user list:

Thanks for checking! Best regards, Bastian

What version of Home Assistant Core has the issue?

2022.12.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Core

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

BTW: The error message itself misses a blank: "Home Assistant auth provider is running in legacy mode because we detected usernames that are case-insensitiveequivalent." "Home Assistant auth provider is running in legacy mode because we detected usernames that are case-insensitive equivalent."

[quadroluxinator]

Same message here, username is lower case only (rhasspy-user)

[7ooL]

I get same error in my logs, do I need to add a capital letter to usernames? What are the username requirements?

[Bastian007]

Still occurs from time to time.

Home Assistant OS: 2023.5

[Lantoit]

Same Problem: Logger: homeassistant.auth.providers.homeassistant Source: auth/providers/homeassistant.py:330 First occurred: 14:26:01 (1 occurrences)

Last logged: 14:26:01

Home Assistant auth provider is running in legacy mode because we detected usernames that are case-insensitiveequivalent. Please change the username: 'nspanel'.

Home Assistant 2023.6.1 Supervisor 2023.06.1 Operating System 10.2 Frontend 20230608.0 - latest

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.