The “login” keyword enables you to log on to the manager and run the CLI commands as a different user than the default user. The default user is representing the user as you are currently logged on at the console from where the CLI command is launched. For example, if you log on to system as user “hugo” and launch the following command:
cadsmcmd local mgr_1 verbose
The CLI connects to the manager “mgr_1” for the “default user”. The CLI records this in the “Connecting” message:
Connecting to manager “mgr_1” as user “<default user>”…
It tries to establish the session to the manager as the current user “hugo”. If this user is not known to mgr_1 or has a different password than the session establishment fails. In this case, use different credentials to authenticate the session.
login[=loginID[:password]]
The information passed with the “login” keyword has changed with Client Automation Release 12.9 according to a different authentication method used by Client Automation Release 12.9 compared to USD 4.0. The login process requires information about the security provider, the security authority, the user id, and the user password. The password is passed with the password parameter while the security provider, the security authority, and the user id are passed with loginID. The loginID is build as
\”<security provider>://<security authority>/<user id>\”
Note: The quotes (”) are mandatory. Otherwise the CLI is not able to process the login information correctly. As the quotes has to be interpreted by the cadsmcmd and not by the shell or command prompt they should be protected by a preceding backslash (\).
A security provider could be a Windows system identified by “winnt” or a Linux system identified by “unixl”. The security authority could be a domain or the addressed system. Consider the CLI should log in with the verbose interface to Linux system “lx_sy_1.myCo.com” as “root” with password “5k7zpq]r”. Launch the following command:
cadsmcmd local lx_sy_1 verbose login=\”unixl://lx_sy_1.myCo.com/root\”:5k7zpq]r
The CLI will record this by the message:
Connecting to manager “lx_sy_1” as user “unixl://lx_sy_1.myCo.com/root”…
If the verbose interface should be started for the Windows manager “win_sy_01” and user “myid” for the password “7hj.98,a” the launched command is as follows:
cadsmcmd local win_sy_01 verbose login=\”winnt://win_sy_01/myid\”:7hj.98,a
The CLI records:
Connecting to manager “win_sy_01” as user “winnt://win_sy_01/myid”…
If login is coded with loginID but no password, then the CLI assumes that there is no password for the specified user. If login is coded without userID and password, then the CLI starts a short dialog for acquiring these parameters.
Note: When cadsmcmd is invoked with the login parameter the local parameter should be coded too to enhance security.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|