If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Authentication - ReportNet Installation

Started by tanujachap, 08 Dec 2005 01:01:23 AM

Previous topic - Next topic

tanujachap

Hi..

I m trying to install Reportnet on my windows XP and my DB2 database V7.2 is residing on a different server.

In the  'Authentication' Settings in Cognos Configuration, i hv couple of questions on the types of authentication i get to see.. By default, the type of the authentication is Cognos. How is this different from Cognos Series 7.wht is the difference between Cognos Series 7 and LDAP.i understand LDAP is a third party authentication provider... but wht is Cognos Series 7 authentication for.
we use Netscape Directory server for authentication for the same. 

i was trying to configure the settings for LDAP type of Authentication.
wht is USER LOOKUP .wht has to be keyed in against this option. should it be left blank?
wht is Bind user DN and Passwd.

Any other changes need to be done against the advanced options of LDAP authentication?

Pls. help me in this regards. Pls. feel free to ask me  if u need any more info.


Thanks
Tanuja.






cognosfreelancer

Hello Tanuja

The Cognos authentication provider that you see can be used for allowing annoynmous access.

If you set that to true you will not need to create any other authentication providers.

You create other authentication providers when you do not wish to have annonymous access enabled.

Cognos Series 7 is one of the drop down options you will see when you create this.

The reason this exists as a separate option is that whether Series 7 uses LDAP or .LAE files, it can be managed from within the Access Manager application existing in the series 7 program folder.

If you select LDAP as the authentication provider , you will not be able to manage it from within Access Manager even if it were using LDAP as a the provder.

Configuring an LDAP provider is a far more complicated task then selecting the Active Directory provider.

In case you use the Microsoft AD then I would recommend that you use the built in AD provider than the LDAP provider. The difference in performance is too substantial to do other wise.

USerlookup field is used for mapping LDAP attribuutes to the user variable. Normally it is sAMAccountName.

A Bind DN is the Distinguished name used to bind into the LDAP hierarchy. The LDAP provider will use this account's authority to traverse the tree. So make sure this account has 'trusted for delegation' attribute set to true in LDAP.

You will need to configure the Base DN property.The provider will traverse the LDAP hierarchy from that point downwards. Easiset way is to copy the path from an LDAP browser.

Make sure that the user lookup field and the object class fields are indexed in the LDAP.

Wow, this must be my longest post.  ;D

HTH
Naveen