Opencart 2 3 Invalid Token Session Please Login Again

Trouble

Cognos Controller ten.iii.1 (and afterwards) comes bundled with Cognos Analytics (CA). CA can be used to provide Cognos (CAM) authentication. Customer has decided to deploy Controller via CAM hallmark. In addition, they would like to configure CAM to use Single Sign On (SSO). - In other words, the user does not have to type their username and password (instead, their Windows user/password gets automatically passed onto the Cognos CAM hallmark machinery). They have therefore tried to configure SSO as described inside divide Technote #2002465. - In other words, they have created a Windows IIS website (called 'ibmcognos') and configured many settings (within IIS) to convert it into an SSO mechanism for CA. Afterwards, user launches the Cognos Connection website (for CA). - Specifically they launch http:///ibmcognos/bi An error appears.

Symptom

Invalid login response

Crusade

Incorrect configuration of either:

• IIS (web server) configuration
• Cognos Configuration

Scenarios

There are many unlike potential misconfigurations that can cause the problem. Below are a list of scenarios that accept been seen.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IMPORTANT: SSO is highly customisable. Non all environments volition be identical. Therefore, take care earlier making any changes listed below. It may be that the specified alter is not applicable to your environment.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

• Scenario #1 - The SSO Rules "SSO Login" and "Legacy SSO" are enabled (inside IIS configuration hither: Default Website-->Alias-->bi-->URL Rewrite)
• This is not correct if the Content Manager has "Employ External Identity" set to Fake
• TIP: For more than details, see split IBM Technote #2015402.
• Scenario #ii - The settings "Anonymous Authentication" and "Windows Authentication" are incorrect for the IIS websites 'bi' and 'sso'
• TIP: For more details, see carve up IBM Technote #2014747.

• Scenario #3 - The rewrite rules were configured for an incorrect application proper noun
• TIP: For more details, see separate IBM Technote #2012485.

• Scenario #iv - 'web.config' file is overriding the correct IIS settings
• TIP: For more details, run across separate IBM Technote #2013573 (plus as well 2009885).

• Scenario #v - Wrong settings inside 'Cognos Configuration'
• TIP: For more details, see separate IBM Technote #2013566

• Scenario #6 - Incorrect value for 'Response' (inside "system.webServer" - "httpErrors")
• TIP: For more details, come across separate IBM Technote # 2004766
• Scenario #7 - Miscellaneous incorrect settings
• TIP: For more details, see separate IBM Technote # 2008522

Resolving The Problem

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Important: SSO is highly customisable. Non all environments will exist identical. Therefore, take care before making whatever changes listed below.

• It may be that the specified alter (listed below) is not applicable to your surroundings.

Also, every bit a precaution, please accept appropriate steps earlier making any changes.

• For case, take a consummate VMWare/ESX epitome backup of your virtual server

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Scenario #i
In 1 real-life case, the solution was to disable the rules "SSO Login" and "Legacy SSO".

• TIP: For more than details, run across split IBM Technote #2015402.

Scenario #2
Modify the hallmark settings for the IIS websites 'bi' and 'sso'.

• TIP: For more details, run across split up IBM Technote # 2014747 .

In one real-life case, the right settings were:

*bi*
• Bearding Authentication = "Enabled".
• Windows Authentication = "Disabled".

*sso*
• Bearding Authentication = "Disabled".
• Windows Authentication = "Enabled".

Scenario #three
Alter the URL rewrite rules, so that they refer to the right awarding name..

• TIP: For more than details, see separate IBM Technote #2012485.

Scenario #4
Delete the relevant 'web.config' files (for example from "webcontent", "webcontent\bi" and "cgi-bin" directories). Afterwards, re-run the SSO configuration changes.

• TIP: For more details, run into separate IBM Technote #2013573 (plus also 2009885).

Scenario #five
Change the settings inside 'Cognos Configuration' to exist correct.

• TIP: For more details, see separate IBM Technote #2013566

Scenario #half-dozen
Modify the value for 'Response' (inside "system.webServer" - "httpErrors") to exist 'Laissez passer Through'

• TIP: For more than details, see split IBM Technote #2004766

Scenario #vii
Check/modify various miscellaneous settings.

• TIP: For more than details, see dissever IBM Technote # 2008522

Workaround
Launch the CA website via the dispatcher URL (instead of IIS).

• In other words, use a URL like to: http://<servername>:9300/bi/v1/disp

Related Information

[{"Product":{"lawmaking":"SS9S6B","label":"IBM Cognos Controller"},"Business concern Unit":{"lawmaking":"BU059","label":"IBM Software westward\/o TPS"},"Component":"Controller","Platform":[{"code":"PF033","characterization":"Windows"}],"Version":"10.3.1","Edition":"","Line of Business":{"lawmaking":"LOB10","label":"Data and AI"}}]

rosenblumexplas1964.blogspot.com

Source: https://www.ibm.com/support/pages/troubleshooting-invalid-login-response-error-when-launching-cognos-analytics-bundled-cognos-controller

Share this post