Issue Details (XML | Word | Printable)

Key: CORE-3962
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Luciano Mendes
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Trusted Authentication is not working for Windows 8

Created: 27/Oct/12 04:06 PM   Updated: 11/Aug/19 09:44 PM
Component/s: Engine
Affects Version/s: 2.5.1, 2.5.2, 2.5.8
Fix Version/s: None

File Attachments: None
Image Attachments:

1. Win8_TrustedAuthentication.png
(11 kB)
Firebird (x64) RC1;
Windows 8 Pro;

 Description  « Hide
Steps to reproduce the issue:
1- Create a local Windows 8 account using a Windows Live ID (e.g.:;
2- Setup the Firebird (x64) RC1 and make sure that "Authentication = mixed" in the firebird.conf file;
3- Try to connect in a existent database using Trusted Authentication;

Actual result:
Engine Code: 335544882
Engine Message: Login name too long (38 characters, maximum allowed 31)
See: Win8_TrustedAuthentication.png

Expected Result:
The user should be able to connect in the database using Trusted Authentication;

Additional Information:
This issue is not reproducible on Windows 7;
User name = Luciano

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Arioch added a comment - 11/Aug/19 09:44 PM
This would require introducing user pseudonymes/aliases into security2.fdb (and into corresponding auth plugin for FB3), so that this substitute be used by Firebird instead of ""

Which would unleash next batch of quesitons: who is allowed to modify this table? where is it stored - per-computer, per-NT-domain, per-database?

I wonder what is maximum username length on UNIX and what FB would do if the username in Linux/BSD exceeds FB's 32 characters frame...