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

have installer ask for and set SYSDBA password & port [CORE2536] #2946

Open
firebird-automations opened this issue Jul 3, 2009 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Jim Michaels (jmichae3)

Votes: 1

the installer should ask for and set the SYSDBA password. all good databases do this.
please don't leave the sysadmin to hunt for more instructions on how to properly install the database.
make it easier when you can.

Show the default database port in the port number textbox during installation when asking the user which port to install the server on. (when I installed mine, I had absolutely no clue as to what port the server was going to serve on by default, so I didn't know if the default would conflict with any other ports I currently had, and this was a source of consternation)

http://www.autoitscript.com/autoit3/
Auto-it3 is a scripting language like VB except that it basically works with one dialog. it has ShellExecute and ShellExecuteWait functions. If your gsec program gets fixed properly, it is possible to use a very simple 20-to-30-line program to call gsec to change the SYSDBA password.

I suggest having a "cancel" button, a "change password" button, a static text that says "userid: SYSDBA", and a static text that says "password" next to the password.
Leave some obvious space between the two static texts, but keep the two password items close together.

I might be able to write the code for you if you get gsec working and the command-line parameters for modifying users don't change (currently the command does not work).

@firebird-automations
Copy link
Collaborator Author

Commented by: @reevespaul

The installer is intended to be as simple as possible. Lack of choice is a deliberate design decision.

The primary use case scenario for the windows installer is for deployments to developers, and there is no need to change the default password. Developers want and expect the standard password. And it is expected that development deployments are made within a secure environment. If that is not the case then the Firebird password is probably the least of problems to worry about.

Deployment for production use is outside of the scope of the installer. The intention under these circumstances is that the installer is deployed within an installer that will manage application or site specific installation details.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Paul, I've to say that I *completelly disagree*.

@firebird-automations
Copy link
Collaborator Author

Commented by: Jim Michaels (jmichae3)

there is no way to create users without any access to the SYSDBA password. and you can't do that without changing it since it is not in the documentation.

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

1 participant