New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trusted Auth and long login with non-english characters [CORE5866] #6125
Comments
Commented by: Sean Leyne (seanleyne) User ID string are Object IDs, thus are restricted to the limitations which applies to all database objects (31 characters). The implementation of Trusted Auth functionality is constrained by the systemic/engine/base schema limitations. |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff An issue will be gone in FB4 - it has increased limit of SQL identifiers length (63 unicode chars). In FB3 you can avoid this using mapping - create mapping from "DOMN\КрасноруцкаяАА" to something like "DOMN\Krasnorutskaya". |
Commented by: Sean Leyne (seanleyne) Create a "mapping" how? |
Commented by: @AlexPeshkoff CREATE MAPPING Krasnorutskaya USING PLUGIN WIN_SSPI FROM USER 'DOMN\КрасноруцкаяАА' TO USER "DOMN\Krasnorutskaya"; And yes - there is a bug to fix: global mapping can not be created. |
Modified by: @AlexPeshkoff |
Commented by: @AlexPeshkoff Mentioned behavior is as designed and not a bug. SQL identifier length is extended in FB4 but it's also limited. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Maxim Kuzmin (cybermax)
Is related to CORE749
Relate to CORE5904
We using Windows trusted authentication (FB 3.0) and user login's with non-english characters as surname and initials. But in case of long a surname (like "DOMN\КрасноруцкаяАА"), error occurs: "Login name too long (33 characters, maximum allowed 31) and user can't attachment to database.
The text was updated successfully, but these errors were encountered: