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

 

11.0.6 Invalid login response with SSO Login URL Rewrite rule

Started by Bluefyre, 12 Apr 2017 09:06:58 AM

Previous topic - Next topic

riley.murphy

I had a heck of a time with this error, took me several days to figure out.

In my case, it was only happening for my specific active directory user, other test/service AD accounts could login fine.

I ended up recreating the content store database, and the issue went away after that.
My user/AD profile must have gotten corrupted in the content store somehow.
Hopefully this information saves some headaches out there.

This is the solution I got from cognos.

"I am glad that you were able to resolve the issue. If it's just one user qho couldn't login then yes. this is likely to be an issue with the specific user credentials saved in the LDAP server or in Content store.
To check the Cognos Content Store for any inconsistencies or corruption, you can always performa consistency check on the CS DB before you drop the entire DB and recreate the tables from scratch.

Following is the link to the KB doc for CS consistency check:

https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.ug_cra.10.2.2.doc/t_asg_mt_consistencycheck.html

"


Bluefyre

Forgot I started this thread. We just ended up waiting for 11.0.7. Thankfully that resolved all our problems. It has been a hair pulling experience for a year trying to get Cognos 11 to our customers. Finally we are getting there.

ckeatonLPA

So I tried about everything on this thread.  Then a genius co-worker shared with me the following, WHICH SOLVED MY PROBLEM ENTIRELY:

1.   Click on the SSO application under ibmcognos.
2.   Double click on the Handler Mappings icon in the middle pane.
3.   Double Click on the Cognos SSO handler.
4.   Click on the Request Restrictions... button.
5.   Click on the Verbs and Access tab. Don't change anything, just click on them.
6.   Click the OK button.
7.   Click the OK button.
8.   You should get a Yes/No dialog. Click on Yes. (If you don't get the dialog try again, it seems to be the key.)
9.   Restart IIS for good measure.