One aspect of securing the application is preventing unauthorized users from logging in. Another is limiting the use of functionality that is based on the role of the logged-on user. Securing the application includes the following mechanisms:
The product uses CA EEM to authenticate users at login. CA EEM compares the credentials users enter at login with user name and password combinations in User Accounts. The user can log in only if CA EEM finds a match.
Administrators can help protect the product from an unauthorized login by requiring users to change passwords periodically and by suspending or disabling default accounts. For more information, see:
The product uses CA EEM to authorize logged-in users. CA EEM lets users perform tasks only on those parts of the user interface for which they are authorized. Authorization for the PAMAdmins, Designers, and Production Users groups is set by default. Users added to these groups inherit the authorization.
Administrators can define role-based security so that users who belong to different groups access only parts of the product necessary for the role they perform. Administrators can also use CA EEM policies to assign trusted users to activities for which misuse can cause the greatest damage. This aspect of access control is a separate consideration from the group role to which individual users are assigned.
|
Copyright © 2014 CA.
All rights reserved.
|
|