3/6/2012 10:05:49 AM
Greetings, I am evaluating Secret Server, and so far I am impressed. I am wondering about the ability to change ODBC settings on a server as an action after the SQL Server account has been changed.
Here is the scenario:
We have an application server that is tied to a SQL server. The application makes its connections via SQL Authentication that has been preprogrammed as an ODBC system DSN. Occasionally the application needs updated, however the updater software requires the application team to type the SQL Auth password. This mean I as a server admin must give over the password and let the app team upgrade their SW. After that I must go back into SQL, change the password and change it again in the ODBC settings. This is a lot of manual steps. I was hoping that Secret Sever would help me by doing the following:
1. The app team checks out the Secret
2. The Current Password is displayed
3. The App Team preforms the upgrade
4. The app team checks in the Secret
5. Secret Sever would change the password of the viewed SQL account on the correct SQL server
6. Secret Sever would update ODBC System DNS of the viewed SQL account on the correct Application server
Is this solution even possible with the current version? I am thinking it is not because one secret needs to track the SQL server, the Application Server(s), and the system DSN name.