Author Topic: Upgrading 11.0.7 to 11.2.1 - Authentication in all namespaces  (Read 610 times)

Offline Rehtaeh209

  • Associate
  • **
  • Join Date: Nov 2021
  • Posts: 2
  • Forum Citizenship: +0/-0
Hello,

I have a two system environment in a pretty small shop.  I was able to upgrade our test environment with little trouble from 11.0.7 to 11.2.1.  When I went to upgrade the production environment I get the AAA-AUT-0013 The user is already authenticated in all available namespaces error when I go to the web login page. 

I have already reviewed and done everything on this page: https://www.ibm.com/support/pages/aaa-aut-0013-user-already-authenticated-all-available-namespaces-1
Quote
Modify the gateway URI, Dispatcher URI and content manager URI from localhost to actual server name (or IP address, or FQDN)
Set the IBM Cognos Application Firewall to True
Test all the namespaces and make sure all test successfully. (if these fail then make sure bind credential for the namespace are set correctly)
In the namespace, make sure selectable for authentication is set to True.

As well as this page: https://www.cognoise.com/index.php?topic=34570.0
Quote
Actions
Edit Global Configuration...
In Cookie Settings
    Domain = your server name (like in Local Configuration/Environment/Controller URI for gateway = http://server name/ibmcognos/controllerServer)
    Path = /

We use Active Directory to connect via IIS.  I've looked through all of those settings and can't find anything.  I even walked through the IIS configuration instructions here: https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=services-configuring-iis-in-cognos-analytics

If someone has any additional thoughts of what I could try, I'd greatly appreciate it.

Offline Rehtaeh209

  • Associate
  • **
  • Join Date: Nov 2021
  • Posts: 2
  • Forum Citizenship: +0/-0
Re: Upgrading 11.0.7 to 11.2.1 - Authentication in all namespaces
« Reply #1 on: 30 Nov 2021 05:13:21 pm »
I am unsure how/why it happened:
During the upgrade the user I had previously set on our database server for our content store connection was deleted/removed from the database users.  I added back the user on the database then Started the Cognos service to resolve the issue.