Administering › Managing Profile Objects

Managing Profile Objects

Profile objects let multiple LDAP users log on to CA View or CA Bundl with an alternate mainframe user account. You can create a standard profile object or an LDAP mainframe hybrid profile object.

Normally, a profile maps multiple LDAP users to a single mainframe account. However, the build in the LDAP mainframe hybrid profile lets each user authenticate through LDAP. The user can then use the LDAP passwords as mainframe passwords.

Note: If you delete a profile, a message indicates that the profile was successfully deleted. If the message indicates that the profile was not deleted, there are roles still assigned to the profile.

Standard Profile

The standard profile object provides a proxy set of mainframe credentials that all LDAP users share in a particular role. All LDAP users must have an assigned profile for their role, which determines their access to CA View or CA Bundl repositories. These credentials include either mainframe security credentials or internal security credentials for the various CA View or CA Bundl repositories.

Note: We recommend that all profiles use mainframe security credentials. Otherwise, verify the validity of the profile credentials for each CA View and CA Bundl system.

Profile Access

• Role access is limited to material its profile credential have access to on the CA View and CA Bundl systems.
• Role or repository settings can further limit access and permissions of users.
• If a user has access to data on specific repositories, the users can only gain access to the data of their role profile credentials.
• The standard profile uses a single set of mainframe credentials. All users that use this profile have certain limits on their actions, no matter which role uses the profile.

  Note: Administrators must be aware that the credentials supplied by a profile can expire in a mainframe security package. If they expire, a user from a similar role (or the System Administrator) must update the credentials.

  When assigning a subscription to a role which uses a profile, verify that the reports in the subscription are accessible by the profile and role. It may be confusing to assign subscriptions of reports from various repositories when the profile cannot access some of the repositories.

LDAP Mainframe Hybrid Profile

CA OM Web Viewer creates the LDAP profile automatically. This built-in profile does not supply a single mainframe credential for all the users in the profile; instead, it uses the LDAP credentials supplied by each individual user.

Consider the following information:

• Use this profile with caution, because it requires that the LDAP and mainframe credentials of a user are synchronized.
• This profile is named LDAP and CA OM Web Viewer creates this profile automatically. This built-in profile does not supply a single mainframe credential for all the users in the profile. Instead, it uses the LDAP credentials that each individual user supplies.
• If you delete this profile, you can recreate it by creating a profile named LDAP. Use LDAP for the user name and password.

  For example, a user logs in to LDAP with the following credentials:

  User: user1

  Password: pwd1

  CA OM Web Viewer sends these credentials to the mainframe.