Use this command to perform the following functions:
You need to run this command in the following scenarios:
The inputs required while running this command are same as those required while configuring details of the BMC Atrium Single-Sign On server while using the installation wizard.
If you are installing the product for the first time, use the installation wizard for configuring Atrium Single Sign-On. To do this, you need to perform a custom installation of the Console Server and then provide details of the Atrium Single Sign-On server that you want to configure. For more information, see Installing in a multiple-server environment.
To understand the syntax and examples, see:
Prefix this command with the following, as appropriate:
enablesso -d <hostName> -p <portNumber> -u <userName> -w <password>
-sd <AtriumSSOHostName> -sp <AtriumSSOPort>
-ss <AtriumSSOProtocol> -su <superusername> -sw <superuserpassword>
-tenant <tenant> -usermigrationscope <usermigrationscope> [-passworddefaultsuffix <PasswordSuffix>]
[-l <locale>] [-v] [-s]
Angle brackets (< >) indicate a variable value that needs to be user defined.
Square brackets ([ ]) indicate optional parameters.
The following table describes the parameters used in the syntax:
|Host name of the Console Server|
|Port number of the Console Server.|
|User name to use to connect with the Console Server.|
|Password corresponding to the user name to use to connect with the Console Server.|
|Fully Qualified Domain Name (FQDN) of the Atrium Single Sign-On server.|
Port number of the Atrium Single Sign-On server.
The default port is 8443.
For more information about the ports supported, see Communication ports and protocols.
Protocol to connect with the Atrium Single Sign-On server.
By default, the value is HTTPS.
User name for connecting with the Atrium Single Sign-On server.
By default, the value is set to amadmin. Leave the default value unchanged.
Password for connecting with the Atrium Single Sign-On server (specified in the plain text format).
The password corresponding to the default user name is the same as what you provided while installing the Atrium Single Sign-On server.
Name of the tenant (also known as Realm in Atrium Single Sign-On) that you configured while integrating IT Data Analytics with BMC TrueSight Operations Management. For more information, see Integrating with TrueSight Presentation Server.
If you want to use a standalone instance of the Atrium Single Sign-On server, then provide the name of the tenant that is present on the Atrium Single Sign-On server.
By default, the value is set to BmcRealm.
Determines whether you want to create all or only the default users (including associated user groups) existing in IT Data Analyics on Atrium Single Sign-On.
Depending on the scope that you decide, the value can be one of the following:
By default, the value is set to DEFAULT.
(Optional) Provide a suffix so that the password for users in Atrium Single Sign-On is set to the "user name_suffix".
The suffix provided will be case sensitive and will be appended to all the users in Atrium Single Sign-On.
The password in Atrium Single Sign-On must be at least seven characters long.
Example: If the user name is John and the suffix provided is BMC, then the password will be, John_BMC.
If you do not provide this input, then by default the "ITDA_USER" suffix is used.
(Optional) Indicates the locale in which you want to display messages when the command is run.
You can set one of the following locales:
By default, the messages are displayed in the locale of the system on which the CLI is run.
The value can be set to one of the following depending on the locale you choose:
Example: If you want to set the locale as Simplified Chinese, you need to specify,
|(Optional) Version of the IT Data Analytics product.|
|(Optional) Indicates an HTTPS connection.|
The following example provides the input for configuring the Atrium Single-Sign On server:
After running the command, it is possible that you might not be able to log on to the product. Such a scenario can occur due to the difference in how the user, user group, and role mapping was handled prior to version 2.1.00 of the product.
The following table provides a comparison of the user authentication approaches in the different versions.
|Version 2.0 and earlier||Version 2.1 and later|
For more information, see Troubleshooting common issues by selecting the upgrade-related and accessing the product-related categories.