enablesso
Use this command to perform the following functions:
- Configure the BMC Atrium Single Sign-On server on IT Data Analytics.
- Create users (along with associated user groups) existing in IT Data Analytics on BMC Atrium Single Sign-On.
You need to run this command in the following scenarios:
- If you have upgraded from an earlier version of the product and want to start using BMC Atrium Single-Sign On with IT Data Analytics.
- If you performed a new installation of IT Data Analytics without configuring details of the BMC Atrium Single-Sign On server and now you want to start using BMC Atrium Single-Sign On with IT Data Analytics.
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.
To understand the syntax and examples, see:
Related topics
BMC Atrium Single Sign-On resources
To access information about installing and configuring BMC Atrium Single Sign-On, see the online documentation for BMC Atrium Single Sign-On version 9.0.
To create, edit, or delete users by using BMC Atrium Single Sign-On, see Managing users.
To create, edit, or delete user groups by using BMC Atrium Single Sign-On, see Managing user groups.
Syntax
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:
Example inputs
The following example provides the input for configuring the Atrium Single-Sign On server:
admin12345 -tenant BmcRealm -sd clm-pun-016060.bmc.com -sp 8443
-su amadmin -sw bmcAdm1n -usermigrationscope ALL
-ss https -passworddefaultsuffix default
Troubleshooting user mapping conflicts
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.