[GH-ISSUE #22521] feat: Optional Unicode support for usernames (NFC normalised, opt-in) #19732

New Issue

GiteaMirror · 2026-04-20T02:14:34-05:00

GiteaMirror commented

2026-04-20 02:14:34 -05:00

Originally created by @Otzie2023 on GitHub (Mar 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22521

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

The current restriction to ASCII can be problematic for:

Users with non-Latin names
Systems with international user environments
Consistency with other systems that support Unicode usernames
Users who want freedom

Many modern systems already support Unicode usernames.

Desired Solution you'd like

The current Home Assistant usernames only allow ASCII characters (not the GUI/display names). I would like to propose optionally supporting Unicode characters for usernames.

The proposal would be:

Usernames may contain Unicode characters (certain blocks could be whitelisted or blacklisted)
All usernames must be NFC-normalized
This feature must be explicitly enabled in a configuration file (opt-in)
By default, the current behavior (ASCII-only) remains

Additional security measures:

When creating a non-ASCII username, a warning should always appear stating that this may lead to potential compatibility issues.
This would be similar to the --badname option of useradd on Linux systems.
This helps prevent users from accidentally creating problematic usernames.

Alternatives Considered

This change could bring the following advantages:

Better internationalisation
More consistent support for non-Latin names
Continued full backward compatibility, as the feature remains disabled by default
It doesn't hurt anyone
More freedom for the user

Low risk due to:

Explicit opt-in
Warnings for non-ASCII names
NFC normalisation

In addition, it could be clearly documented that:

only the functionality within the basic Home Assistant installation is guaranteed
integrations or plugins may not work as a result and the functionality of plugins is not guaranteed

This keeps responsibility clear and the risk to the core system low.

Additional Context

No response

Originally created by @Otzie2023 on GitHub (Mar 10, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22521 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description The current restriction to ASCII can be problematic for: - Users with non-Latin names - Systems with international user environments - Consistency with other systems that support Unicode usernames - Users who want freedom Many modern systems already support Unicode usernames. ### Desired Solution you'd like The current Home Assistant usernames only allow ASCII characters (not the GUI/display names). I would like to propose optionally supporting Unicode characters for usernames. The proposal would be: - Usernames may contain Unicode characters (certain blocks could be whitelisted or blacklisted) - All usernames must be NFC-normalized - This feature must be explicitly enabled in a configuration file (opt-in) - By default, the current behavior (ASCII-only) remains Additional security measures: - When creating a non-ASCII username, a warning should always appear stating that this may lead to potential compatibility issues. - This would be similar to the --badname option of useradd on Linux systems. - This helps prevent users from accidentally creating problematic usernames. ### Alternatives Considered This change could bring the following advantages: - Better internationalisation - More consistent support for non-Latin names - Continued full backward compatibility, as the feature remains disabled by default - It doesn't hurt anyone - More freedom for the user Low risk due to: - Explicit opt-in - Warnings for non-ASCII names - NFC normalisation In addition, it could be clearly documented that: - only the functionality within the basic Home Assistant installation is guaranteed - integrations or plugins may not work as a result and the functionality of plugins is not guaranteed This keeps responsibility clear and the risk to the core system low. ### Additional Context _No response_

GiteaMirror closed this issue

2026-04-20 02:14:34 -05:00

GiteaMirror commented

2026-04-20 02:14:35 -05:00

@pr-validator-bot commented on GitHub (Mar 10, 2026):

⚠️ Missing Issue Title Prefix

@Otzie2023, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support

Example: bug: Login fails when using special characters in password

@pr-validator-bot commented on GitHub (Mar 10, 2026): # ⚠️ Missing Issue Title Prefix @Otzie2023, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`

GiteaMirror referenced this issue

2026-04-25 08:30:51 -05:00

[GH-ISSUE #19732] Open WebUI API Works with normal models but fails with RAG/Knowledge Database on OpenAI-Compatible Clients #34501

GiteaMirror referenced this issue

2026-05-05 21:16:42 -05:00

[GH-ISSUE #19732] Open WebUI API Works with normal models but fails with RAG/Knowledge Database on OpenAI-Compatible Clients #57638

Sign in to join this conversation.