Using a Domain Name when caching credentials for UNIX application servers
By Fat Bloke on Apr 17, 2007
Here's a tip which makes life easier for users logging in to multiple UNIX backends...
Imagine you have a large number of UNIX or Linux application servers.
And you use the same credentials to login to all of them. (e.g. they may be using a central LDAP server,or NIS+)
Normally, when you launch an app on one of these servers and SGD doesn't have a cached set of credentials, the user is prompted for a username/password. In this scenario, where there are a lot of servers, this can become tedious for the user.
So here are 2 suggestions:
1. If you use the same credentials on the SGD server and on the UNIX app servers you can enable the "Try SGD password". This is enabled in the Array Manager thus:
2. If the SGD server uses different credentials from all the 3rd tier UNIX app servers, label the app server objects as being in the same domain. You do this by setting the inappropriately named "Windows NT Domain" attribute on all your app servers, to the same thing, e.g. "DatacenterServers"
Now the credentials are cached against the domain rather than a single app server.
So when your users launch a UNIX app now, on any other UNIX server in the same domain, they won't get prompted.