Login Objects and Account Credentials

As an Administrator, you use Login Objects to store the account credentials that Agents need for accessing Deployment Targets. The account credentials save login information for either a host (operating system) or a back-end system (for example, Subversion) and they can be related to single Deployment Targets or shared between a set of them (for example, shared account).

Important! The actions that you can perform depend on your folder permissions, see: Folder Permissions.

This page includes the following:

Overview

The following graphic illustrates the role of Login objects in the Deployment Model. Select the image to expand it.

Graphic depicting role of login objects in deployment model

Login Objects are stored in separate folders for access rights and permission control. They are linked to Deployment Profiles to allow tasks to be executed under different accounts for each Application and Environment.

The account credentials are a part of the Login object definition. They provide the host and the back-end system names, the user and the password. For example, the host could be the operating system and the back-end system, Subversion.

Viewing Login Objects and Login Credentials

  1. Open the Release Automation perspective.
  2. In the Navigator pane, click Settings > Logins. The list of CDA login objects is displayed.
  3. Select a Login object and click Credentials in the toolbar to display the login credentials in the AWI. See: Login (LOGIN)

Tip: For more information about how to search for entities and narrow down the results, see: Global Search

Creating Login Objects

  1. Click the Create button in the toolbar.
  2. All fields on the Create Login dialog are mandatory.

    The Name must be unique and can only contain alphanumeric characters, blanks, ., -, _, @, $, #

  3. Click Create.

Editing the Properties of a Login Object

Use the Login Object Sidebar that is displayed next to the Logins list to edit the Login object properties:

Deleting Login Objects

Note: You may only delete the entity when you have the appropriate permission on the containing folder (see Security Concept) and all of the listed conditions are met.

Conditions to delete entities of type LoginObject