Configuring Auto-registration of Users

You can configure auto-registration of users for integrating with products, such as Release Manager, where you want to access Deployment Automation functionality without having to manually create matching users in Deployment Automation or require an inconvenient login each time users access the integrating functionality.

Single Sign-On User List

After you have logged onto Deployment Automation through Release Manager the first time with a particular user ID, that user ID is created and assigned to the Read Only Group in Deployment Automation.

You can view the users authenticated through Single Sign-On in Administration > Security > Authentication (Users) in the Authentication Realms pane.

See Authentication Realms and Users.

Default Security Group

When users are auto-registered, they are added to the default security group. For a native Release Manager installation of Deployment Automation, the Read Only Group is set as the default security group.

Default security group is set in Administration > System > System Settings.

See System Settings.

Group Membership

Auto-registered users are automatically added to the Read Only Group.

If you want a user to have administrative privileges in Deployment Automation, so that they can create Deployment Automation applications, environments, and component versions from Release Manager, you must add them to the Admin Group.

Tip: The default user, admin, exists in the SBM and Deployment Automation sample databases, so admin is already part of the Admin Group if you start with the sample databases in your installation.

You can view the membership for groups in Administration > Security > Authorization (Groups) in the Authorization Realms pane.

See Authorization Realms and Groups.

Default Permissions

The Read Only Group by default has read only permissions, as the name implies. You can change the default permissions if you want your auto-registered users to have more permissions.

Note: If you want a user to have administrative privileges in Deployment Automation, so that they can create component versions from Release Manager, you should add them to the Admin Group rather than expanding their individual privileges or the Read Only Group privileges.

You can change permissions in Administration > Security > Default Permissions.

See Default Permissions.

Related Topics

Single Sign-On (SSO) Configuration