You must use the Cognos® Configuration
and Cognos Connection applications
to configure the IBM® Cognos BI applications to use
the HCL
EMM Authentication
Provider.
Procedure
Complete the following tasks to configure IBM Cognos to
use the HCL
EMM Authentication
Provider:
- On the computer where the Cognos Content
Manager is running, open Cognos Configuration.
- Select Local Configuration > Security > Authentication.
- Right-click Authentication and select New
resource > Namespace.
- Complete the fields as follows, and then click OK:
- Name: Unica
- Type: Custom
Java Provider.
- On the Resource Properties page,
complete the fields as follows and then save your changes:
- NamespaceID: Unica
- Java class name: com.unica.report.adapter.UnicaAuthenticationProvider
- Stop and restart the IBM Cognos BI service.
On
a Windows™ system, sometimes
the Cognos interface indicates
that the service is stopped when it is not. To ensure that the service has really stopped,
use the Windows Administrative
tools to stop the service.
- Under Local Configuration > Security > Authentication,
right-click Unica and select Test.
If Cognos Connection
displays an error, examine the cogserver.log file in
the logs directory of your Cognos installation to determine the problem.
- Log in to Cognos Connection
as follows to verify that the HCL
EMM Authentication
provider is configured correctly:
- If you set the Cognos authentication
mode in the HCL
EMM configuration
properties to authenticated, log in as the
cognos_admin (report system) user.
- If you set the authentication mode in the HCL
EMM configuration
properties to authenticatedPerUser, log in
as the asm_admin user.
If IBM Cognos displays the error "The third-party
provider returned an unrecoverable exception," expand the error message.
If it states "invalid credentials," you made an error entering your
user credentials. Try again. However, if it states "password expired," HCL
EMM expired
the password. Log in to HCL
EMM application
as the reporting system user and reset the password. Then, try logging
in to Cognos Connection again.
If
you still cannot log in to Cognos Connection,
examine the cogserver.log file in the logs directory
of your Cognos installation,
to determine the problem.
- When you can successfully log in to Cognos Connection, open Cognos Configuration again.
- Select Local Configuration > Security > Authentication
> Cognos.
- Disable anonymous access to IBM Cognos BI by setting Allow
anonymous access? to false.
- Save your changes.
- Stop and restart the IBM Cognos service.
If
the IBM Cognos service cannot communicate successfully
with the authentication provider, it cannot start. If the IBM Cognos service fails to start, verify your
configuration by retracing the steps in this procedure.
- Distributed systems only. If your IBM Cognos system has backup Content Managers configured
for failover support, repeat this procedure on all the servers with
Content Manager installed.
Results
At this point, anyone who logs in to an application
on the Cognos system must
be authenticated by HCL
EMM. Additionally,
the authentication namespace Unica now appears
in the IBM Cognos user interface for logon and security
administration tasks.