Reports Integration Guide › Deployment › Map CA Data Protection Reviewers to BusinessObjects Accounts

Map CA Data Protection Reviewers to BusinessObjects Accounts

The iConsole and BusinessObjects Enterprise use trusted authentication to communicate with each other. Using trusted authentication allows users to log on to a system once, without needing to provide passwords several times during a session. In the case of CA Data Protection and BusinessObjects Enterprise, it means that users do not need to log on separately to BusinessObjects when they run a BusinessObjects report or launch InfoView from the iConsole. However, trusted authentication only works if each iConsole reviewer has their own, unique BusinessObjects user account. Therefore, after installing CA Business Intelligence, you must ensure that each of your CA Data Protection reviewers has their own, unique BusinessObjects account.

Note: You set up trusted authentication when you install the BOE Integration for the iConsole (see the later section for details).

Why Is Account Mapping Necessary?

When a reviewer runs a BusinessObjects report or launches InfoView from the iConsole, the reviewer's CA Data Protection account is mapped to a unique BusinessObjects account. This account mapping is performed in the background and serves two purposes:

• First, the mapping allows the iConsole connect to BusinessObjects using the reviewer's BusinessObjects account.
• Second, the mapping allows BusinessObjects Enterprise to apply the reviewer's CA Data Protection security model to the report results. Security models ensure that reviewers can only see events they are permitted to see when running CA Data Protection reports, including BusinessObjects reports for CA Data Protection.

How Do I Set Up Account Mapping?

There are two approaches to enable the account mapping:

• You can manually create the required BusinessObjects accounts.
• You can set up LDAP authentication, whereby BusinessObjects uses an LDAP directory to validate logon attempts by CA Data Protection reviewers.

Both approaches are described below.

More information:

Manually Create BusinessObjects Accounts

Use LDAP Authentication to Validate CA Data Protection Reviewers