/build/static/layout/Breadcrumb_cap_w.png

Deploy ODBC- Settings

Hello all,

we want to deploy ODBC- Settings for a Connection to a SQL- Server. Its very simple with Wise, but how can I deploy the Passwort for the SQL- Authentification? I can put the Username into the LastUser- Attribut (HKLM/Software/ODBC/ODBC.INI/MyEntry/ LastUser=test)... but where I can set the password?

Thx much.
private

0 Comments   [ + ] Show comments

Answers (7)

Posted by: shogun_ro 18 years ago
Orange Belt
0
The password will not be retained.The user should always input the password.
Posted by: private 18 years ago
Senior Yellow Belt
0
no chance? any vbs that could create the entry?
Posted by: aogilmor 18 years ago
9th Degree Black Belt
0
ORIGINAL: private
no chance? any vbs that could create the entry?


vbscipt might be able to do it with regwrite, but why would you want to? violating security just to make things a little easier on the user?...

Just enter it the first time, and it should stick around thereafter. At least I think that's how it works..
Posted by: revizor 18 years ago
Third Degree Blue Belt
0
If there's a specific account used in order to establish ODBC connection, wouldn't it be just a bit more secure to push the logon and password as part of a package, rather than give those out to a user?
Posted by: private 18 years ago
Senior Yellow Belt
0
Hi @ll,

->aogilmor

"violating security just to make things a little easier on the user"
In our Enviroment the User have no permission to set ODBC- Setting....

Now we have a solutions: The Application which use this ODBS- Entry can set it by self... :-)
Posted by: xythex 18 years ago
Orange Senior Belt
0
Microsoft's SQL driver does not retain password information in the registry. You can try connecting with a connection string in your actual application or use a different SQL ODBC driver, or of course the best suggestion is just to have your users enter the password when they connect
Posted by: private 18 years ago
Senior Yellow Belt
0
Thanks to everyone!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ