Configuring IBM® Cognos® to use IBM® EMM Authentication Provider
You must use the Cognos® Configuration and Cognos® Connection applications to configure the IBM® Cognos® BI applications to use the IBM® EMM Authentication Provider.
1.
Complete the following tasks to configure IBM® Cognos® to use the IBM® EMM Authentication Provider:
2.
On the machine running the Cognos® Content Manager, open Cognos® Configuration
3.
Select Local Configuration > Security > Authentication.
4.
Right-click Authentication and select New resource > Namespace.
5.
a.
Name: Unica
b.
Type: Custom Java Provider.
6.
On the Resource Properties page, complete the fields as follows and then save your changes:
a.
b.
Java class name: com.unica.report.adapter.UnicaAuthenticationProvider
7.
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.
8.
Under Local Configuration > Security > Authentication, right-click Unica and select Test.
If Cognos® Connection displays an error, examine the cogserver.log file, located in the logs directory of your Cognos® installation to determine the problem.
9.
Log in to Cognos® Connection as follows to verify that the IBM® EMM Authentication provider is configured correctly:
*
If you set the Cognos® authentication mode in the IBM® EMM configuration properties to authenticated, log in as the cognos_admin (report system) user.
*
If you set the authentication mode in the IBM® EMM configuration properties to authenticatedPerUser, log in as the asm_admin user.
If IBM® Cognos® displays the error "The 3rd 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," IBM® EMM expired the password. Log in to IBM® 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, located in the logs directory of your Cognos® installation, to determine the problem.
10.
When you can successfully log in to Cognos® Connection, open Cognos® Configuration again.
11.
Select Local Configuration > Security > Authentication > Cognos.
12.
Disable anonymous access to IBM® Cognos® BI by setting Allow anonymous access? to false.
13.
14.
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.
15.
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.
At this point, anyone logging in to an application on the Cognos® system must be authenticated by IBM® EMM. Additionally, the authentication namespace Unica now appears in the IBM® Cognos® user interface for logon and security administration tasks.