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

cognos 8.3 connection

Started by Cinu8, 15 May 2008 10:06:18 AM

Previous topic - Next topic

Cinu8

hi every one
i have a problem with our staging cognos connection
we have single sing on enabled
the problem we are getting is when we are on the portal suddenly it time outs and
asks for user name and passowrd not the congos user name and password its Internet Explorer user name and password

i have no idea what causing the problem

please let me know if any body else facing the same issue

cinu



CogDT

What are you using as a web server?  Has single signon always worked previously?  There's both an IE and IIS setting for integrated windows authentication...

ducthcogtechie

Do you have the advanced property "SingleSignonMapping" with the value "IdentityMapping" set in Cognos Configuration, or are you doing a full kerberos to achieve Single Signon?

Cinu8

sorry for the dealy
we are using kerberos..  single signon
and one importent thing is we have multiy domain set up  in one name space AD_Internal
and we are using IIS as web Server

and also we tried setting up in IE like adding url to the Trusted sites and also Local Intranet

ducthcogtechie

If you have a multi-domain in a single forest AD setup, it means you have a few entries in the advanced properties in your AD_Internal namespace connector. What are they?

Cinu8

the advance properties we have is

chaseReferrals       True
multiDomainTrees    True
singleSignonOption  KerberosAuthentication

ducthcogtechie

Like CogDT asked; has it worked in the past?

Cinu8

single sing on is working fin in our current production that is 8.2
but this does not have the multipul domain in one name space
and also the properties set as "SinglesingonMapping" and  value as " IdentifyMapping"



ducthcogtechie

using "IdentifyMapping" means it's not a full kerberos authentication, but using the kerberos mechanism to some extend and using the readout of the remote_user variable to achive single sign-on. That mechanism is less vunorable then a full kerberos.
Do you want to continue to focus on the full kerberos, or add the "IdentifyMapping" to the staging also, which will probably fix your issue?

SomeClown

KerberosAuthentication is an either/or -- the need for the value IdentityMapping is based on how IIS is expecting the credentials.

Go to Microsoft's website and find the Win2K3 utility   WFetch   (should be version 1.4).  Install this to a client machine (not the IIS server).  Open a GET request to your web server,  subdirectory /cognos8  - make the request Anonymous

Read the items returned from the call -- in there you should find the credential type expected (you'll probably see NTLM).  If that is the case (NTLM), then you need to use IdentityMapping for the SingleSignonOption