Subject | Re: [firebird-support] Deploy firebird with another password for sysdba user |
---|---|
Author | Mr. John |
Post date | 2011-11-14T08:33:01Z |
Thanks Helen and Thomas for answers.
Is it a way to change the password automatically,not manually,that I should do with my application install.
Thanks
________________________________
From: Helen Borrie <helebor@...>
To: firebird-support@yahoogroups.com
Sent: Monday, November 14, 2011 10:22 AM
Subject: Re: [firebird-support] Deploy firebird with another password for sysdba user
At 08:37 PM 14/11/2011, Mr. John wrote:
Change the SYSDBA password on the installation of the server at the site where you deploy it. Or, if you have regular users in *your* copy of security2.fdb that have permissions in the database (as you SHOULD have) then back up yours and restore it as sometempname.fdb on the new site.
Then, shut down Firebird, delete the installation copy of security2.fdb, rename the sometempname.fdb version to security2.fdb and then change the SYSDBA password *before* doing anything else.
./hb
[Non-text portions of this message have been removed]
Is it a way to change the password automatically,not manually,that I should do with my application install.
Thanks
________________________________
From: Helen Borrie <helebor@...>
To: firebird-support@yahoogroups.com
Sent: Monday, November 14, 2011 10:22 AM
Subject: Re: [firebird-support] Deploy firebird with another password for sysdba user
At 08:37 PM 14/11/2011, Mr. John wrote:
>Hi ! We need to deploy firebird server with another password for sysdba user.It's not a solution.
>One solution is replacing security2.fdb during install of our application+server.
>
>Is it good solution ?
Change the SYSDBA password on the installation of the server at the site where you deploy it. Or, if you have regular users in *your* copy of security2.fdb that have permissions in the database (as you SHOULD have) then back up yours and restore it as sometempname.fdb on the new site.
Then, shut down Firebird, delete the installation copy of security2.fdb, rename the sometempname.fdb version to security2.fdb and then change the SYSDBA password *before* doing anything else.
./hb
[Non-text portions of this message have been removed]