We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @mrotteveel
When initializing the security database for SRP, two SYSDBA accounts are created if admin option is specified explicitly.
Two sysdba accounts are created if I use (in gsec):
add sysdba -pw masterkey -admin yes
, but not if I use
add sysdba -pw masterkey
Similar if I use in ISQL:
create user sysdba password 'masterkey' grant admin role;
not if I use
create user sysdba password 'masterkey';
In the above case UserManager = Srp, Legacy_UserManager. I also tried with only UserManager = Srp.
I have also tried this in the latest 3.0.2 snapshot, it doesn't happen there.
Commits: 8d95d7c fb22a19
The text was updated successfully, but these errors were encountered:
assignee: Alexander Peshkov [ alexpeshkoff ]
Sorry, something went wrong.
Commented by: @AlexPeshkoff
That's not so easy to reproduce an error in FB3 but if one does:
grant rdb$admin to sysdba granted by John; grant rdb$admin to sysdba granted by Jane;
two records in sec$users might be seen.
Version: 3.0.1 [ 10730 ]
Version: 3.0.0 [ 10740 ]
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 3.0.2 [ 10785 ]
Fix Version: 4.0 Alpha 1 [ 10731 ]
status: Resolved [ 5 ] => Resolved [ 5 ]
QA Status: No test => Done successfully
status: Resolved [ 5 ] => Closed [ 6 ]
AlexPeshkoff
No branches or pull requests
Submitted by: @mrotteveel
When initializing the security database for SRP, two SYSDBA accounts are created if admin option is specified explicitly.
Two sysdba accounts are created if I use (in gsec):
add sysdba -pw masterkey -admin yes
, but not if I use
add sysdba -pw masterkey
Similar if I use in ISQL:
create user sysdba password 'masterkey' grant admin role;
not if I use
create user sysdba password 'masterkey';
In the above case UserManager = Srp, Legacy_UserManager. I also tried with only UserManager = Srp.
I have also tried this in the latest 3.0.2 snapshot, it doesn't happen there.
Commits: 8d95d7c fb22a19
The text was updated successfully, but these errors were encountered: