Skip to content
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

New users or changed passwords in legacy authentication do not work in Firebird 4 [CORE5495] #5764

Closed
firebird-automations opened this issue Mar 5, 2017 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @mrotteveel

I have some problems with using legacy authentication with Firebird 4:

* Using the default existing legacy sysdba/masterke works
* Creating a new user with the Legacy_UserManager (create user ... password '...' using plugin Legacy_UserManager) or with gsec (Legacy_UserManager is the first in the list), and trying to login leads to an authentication failure
* Using gsec to alter the password of the legacy sysdba and then trying to login leads to an authentication failure (even if I changed to masterke or masterkey)

The above seems to suggest that the Legacy_UserManager is broken when hashing passwords

NOTE: Vlad already committed a fix

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Alpha 1 [ 10731 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants