Importing user accounts from HCL Launch to the blueprint design server#
You can use an authentication realm to import user accounts from an HCL™ Launch server. Then, users can log in to the blueprint design server with the same accounts as the HCL Launch server.
- Importing accounts in this way requires HCL Launch version 6.1.1.2 or later.
- Obtain either a token or a user name and password for the HCL Launch server.
-
On the HCL Launch server, set permissions for the users, including giving the users access to components.
Note: When a user logs in to the blueprint designer with an account from HCL Launch, that user sees only the components that they could see if they logged in to the HCL Launch server. If a user logs in with account from a different authentication realm, that user sees the components that are associated with the token or user account that is on the System Settings page.
-
Log in to the blueprint designer as a user with the following System permissions:
- Configure Security
- Manage Users & Groups
- Click Settings > Users.
-
Click Create New Realm.
-
Specify a name and description for the new authentication realm.
-
In the Allowed Login Attempts list, specify the number of times that a user can attempt to log in before the account is locked.
A blank value means that an unlimited number of attempts are allowed.
-
In the Type list, select UrbanCode Deploy.
-
In the UrbanCode Server URL field, specify the full URL of the server, such as
https://ucdserver.example.com:8443
. -
To authenticate with a token, select Token Based Authentication and specify the token in the Token field.
-
To authenticate with a user name and password, clear Token Based Authentication and specify the user name and password.
-
Click Save.
The new realm opens, showing the table of users.
-
Click Import Users, and then click Import to import users from the authentication realm.
Now users can use the same credentials on the HCL Launch server and on the blueprint design server.
Add the users to groups and teams. You must add users to teams to give the users permission to work with blueprints and cloud resources.