Using Groups and Roles to Manage Informatica Access Control

Using Groups and Roles to Manage Informatica Access Control

Predefined Custom Roles

Predefined Custom Roles

Examine the predefined roles in the Administrator tool to determine whether you can assign these roles to your groups. Predefined roles include custom roles for the PowerCenter Repository Service, Metadata Manager Service, and Reporting Service.
The PowerCenter Repository Service roles are designed to create a secure production environment. You might want to assign the predefined PowerCenter Repository Service roles to groups to ensure that users access only what they need. Along with the roles, assign repository object permissions to define a group's level of access to repository objects.
The following table describes how you can use the PowerCenter Repository Service custom roles to create a secure environment:
PowerCenter Repository Service Custom Role
Description
PowerCenter Connection Administrator
Designed for administrators who create connection objects in the Workflow Manager. These administrators have access to source and target databases and applications. Assign this role to a small number of users to maintain source and target security.
PowerCenter Repository Folder Administrator
Designed for administrators who manage repository folders, deployment groups, labels, and queries. These administrators have access to metadata across repository folders. Assign this role to a small number of users to maintain repository folder security.
PowerCenter Developer
Designed for a developer who creates source definitions, target definitions, design objects, and workflows, and who runs and monitors workflows. Assign this role along with folder and global object permissions to restrict user access to the repository metadata that they need.
PowerCenter Operator
Designed for a workflow operator who runs and monitors workflows. In a production environment, you might want to assign this role to an automated user that a script uses to run and monitor workflows. If the automated user’s login credentials are accessed, the user account cannot be used to change repository metadata.
If the predefined custom roles do not meet your needs, you can edit the privileges in the predefined custom roles or create your own custom roles.
The Administrator role is a system-defined role that you cannot edit or delete. The role includes all privileges for the domain and each application service type. In addition, the role bypasses permission checking. Users with the Administrator role can access all objects. To maintain security, limit the number of users assigned the Administrator role.

0 COMMENTS

We’d like to hear from you!