You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2022. It is now read-only.
Hello, i found this while importing users from Active Directory.
The field user does not allow username with character like dot, so a user like john.doe will be imported but no change can be made to them, such user won't be able to properly access or authenticate rendering the provider useless in this scneario.Also character encoding for fields like Firt Name, Last Name and Middle Name need to be able to acept accent mark, since Active Directory and FreeIPA support them.
Expected behavior:
Active Directory and FreeIPA support name convention with especial character like dot (john.doe), Trasa should honor them to keep consitency.
Scope of issue:
TRASA codebase
dashboard
server
mobile app
browser extension
device agent
website/docs
Versions:
TRASA V1.1.4
OS Docker-Compose
The text was updated successfully, but these errors were encountered:
Dragnell87
changed the title
[BUG] Trasa won't accept special chacter in the user field.
[BUG] Trasa won't accept special character in the user field.
Jul 22, 2021
Describe the bug:
Hello, i found this while importing users from Active Directory.
The field user does not allow username with character like dot, so a user like john.doe will be imported but no change can be made to them, such user won't be able to properly access or authenticate rendering the provider useless in this scneario.Also character encoding for fields like Firt Name, Last Name and Middle Name need to be able to acept accent mark, since Active Directory and FreeIPA support them.
Expected behavior:
Active Directory and FreeIPA support name convention with especial character like dot (john.doe), Trasa should honor them to keep consitency.
Scope of issue:
Versions:
The text was updated successfully, but these errors were encountered: