Troubleshooting single sign-on
Several issues are known to occur with single sign-on, for example, if it is not configured properly.
Invalid user name or password error.
Make sure the SSO settings in the TRIRIGAWEB.properties file are set and the application server is restarted.
The user name is case-sensitive in IBM® TRIRIGA®. To see the actual user name that is passed from the web server to IBM TRIRIGA, open the following address in a browser: http://web_server/html/en/default/admin/requestTest.jsp.
You can find the user name in the Request Parameters section, in the Header Parameters section next to getUserPrincipal, or in both sections.
Map labels are shown only in English.
If Esri map labels are shown in English even though your user profile is using a different language, the SSO_BACKING_SERVER_PORT property in the TRIRIGAWEB.properties file might not be configured for the internal non-SSO port.
HTTP requests are no longer forwarded to IBM TRIRIGA.
After you upgrade IBM TRIRIGA on WebSphere® Application Server, IBM HTTP Server no longer forwards requests to IBM TRIRIGA.
You must reconfigure the web server in WebSphere Application Server. One method of reconfiguring the web server is to use the WebSphere Customization Toolbox (WCT). WCT contains the Web Server Plug-ins Configuration Tool, which steps through the process of deleting and re-creating the web server definition for IBM HTTP Server.
If you change the host name, check the plugin-cfg.xml file to make sure that it contains the correct host name specified. Specifically, check the Transport Hostname property. The plugin-cfg.xml is typically in pathToInstall/IBM/HTTPServer/Plugins/config/webServerName/plugin-cfg.xml.