Issue Details (XML | Word | Printable)

Key: CORE-4430
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Mark Rotteveel
Votes: 0
Watchers: 1

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

Properties of user created in Legacy_UserManager padded with space up to 10 character

Created: 15/May/14 03:02 PM   Updated: 23/Sep/15 11:22 AM
Component/s: API / Client Library, Engine, GSEC, Security
Affects Version/s: 3.0 Alpha 2
Fix Version/s: 3.0 Beta 1

Environment: Firebird on Windows 8.1 Update

QA Status: Done successfully
Test Details: Confirmed padded output in WI-T3.0.0.30809 Firebird 3.0 Alpha 2.

 Description  « Hide
A test in Jaybird ( adds a user through the services API and then retrieves the created user to compare the properties. When this test is run against Firebird 3.0 the username, firstname, middlename and lastname properties are padded with spaces (0x20) up to a length of 10 (no padding occurs if the actual value is longer). This only happens when the usermanager is Legacy_UserManager. The properties are not padded when the Srp manager is configured in firebird.conf. Padding also doesn't occur with Firebird 2.5 and earlier.

I am not sure if the problem is with creating or with listing the users, but it also occurs when the user has been created with a CREATE USER statement instead of the service API.

Currently tests on Jaybird use Legacy_UserManager because it doesn't support the new protocol yet.

Note: I have seen the behavior at least since 3.0 Alpha 2 (AFAIR it didn't occur with Alpha 1, but I am not 100%sure), but I didn't have time to investigate closely until today. I tested with the snapshot of today (

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Alexander Peshkov added a comment - 22/May/14 01:20 PM
I've changed format of that fields to be like in 2.5, therefore fresh security database should be used - fix primarily depends not upon code, but upon sec.db format