Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LDAP and Cognos ReportNet Data Source Sign-On/Authentication

Status
Not open for further replies.

akabatman2

Programmer
Feb 25, 2003
102
US
Hi everyone,

Does anyone know how to get Cognos ReportNet to use the same User Name and Password that is entered when logging in to the web front end to be passed to a report's data source so that it could also be used to logon to the database.(ODBC connection)?

On our project, we are trying to implement LDAP as the central authentication repository for ReportNet and our TeraData, Oracle and DB2 Backends. The problem is that ReportNet seems to only allow the hard coded(manually entered) user name and password in the data source(withing CRN).

We are looking for a way to have multiple users be able to logon to ReportNet and in turn have the datasource use their user name and password from LDAP to authenticate to the database. This way the DBA's can monitor security and prioritize per user. This would mean that each user would have their own connection to the backend database, just as they do to ReportNet.

We would want to:

1. Manage user names and passwords in LDAP
2. Users would only have to sign in to the ReportNet front end. Their same UN and PWD would be used to in turn logon to the database.

Is this possible? Any insight would be most appreciated.

Thank you.

 
Here's what we did. We built an application (signon) so that users could add their own database login/pwd to their "accounts" for each database that has access. We disallow all users access to any of the generic database account.

The SDK app basically makes a user signon & authenticate. Then it looks at what DBs a user has access to. Then, the ownership is switched behind the scenes to an admin account, which allows a signon to be stored against the database. When done, they are logged out of the signon app, and there is now a signon that contains their personal credentials.

If you want it all automatic, just enable single-signon on the front. The only time a user would have to enter db password info is if they got access to a new database, or if their password expired.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top