Authenticating against the Application Server

BMC Server Automation uses a variety of security protocols for authenticating against the Application Server. These security implementations and concepts are covered in Administering-security.

To use the BLCLI, you must provide authentication information to the Application Server. You can cache your authentication information for repeated use over a given time period, storing this information in the credentials cache. This topic describes BLCLI authentication requirements, and provides a simple example of how to meet these requirements.

For additional details, see BLCLI-to-Application-Server.

To create an authentication service profile

You can create an authentication service profile by using the blcred utility. The following example shows how to create an authentication service profile with the following values:

  • Name of the service profile = myServiceProfile
  • Host name of the machine running the Application Server = machine1
  • Authentication service port on that machine = 9840 (the default port for the authentication service)
  • Authentication type = srp

Example

blcred authprofile -add -profile myServiceProfile -host machine1:9840 -type srp

For detailed information about all blcred syntax options, see Using-the-blcred-utility.

To populate the credentials cache

You populate the credentials cache using the blcred utility. The following example shows how to populate the credentials cache with the following values:

  • Name of the service profile = myServiceProfile
  • BMC BladeLogic user name = Admin1
  • BMC BladeLogic password = myPassword

Example

blcred cred -acquire -profile myServiceProfile -username Admin1 -password myPassword

For detailed information about all blcred syntax options, see Using-the-blcred-utility.

To use command options for specifying security information

The following example shows how to specify required security information using the following command option values:

  • Service profile name = myServiceProfile
    (-v option)
  • Role = adminRole
    (-r option)

Examples

If you are in an environment with a relatively small number of enrolled servers, try:

blcli -v myServiceProfile -r adminRole Server listAllServers

If you are in an environment with a large number of enrolled servers, for performance reasons, you may want to try this command instead:

blcli -v myServiceProfile -r adminRole JobManagement getJobManagerFullStatus

Tip

n alternative approach is to use environment variables to specify this security information, although command options take precedence. For detailed information about using environment variables with the BLCLI, see Environment-variables.

Related topics

For a complete list of BLCLI command options, see BLCLI-command-options.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*