We are trying to set up SSO for Operator Console, but we keep getting an error. LDAP is working fine, getting Authentication success, but errors are occurring anyway.
We see the following in the samlsso.log:
[http-nio-80-exec-9] DEBUG org.springframework.security.saml.SAMLProcessingFilter 27/10/2020 15:17:32 - Authentication success. Updating SecurityContextHolder to contain: org.springf[email protected]74049ae1: Principal: <emailaddress>@<domain>.com; Credentials: [PROTECTED]; Authenticated: true; Details: null; Not granted any authorities
And this in the wasp.log:
Oct 27 15:17:03:321 ERROR [http-nio-80-exec-6, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/operatorconsole_portlet].[rest]] invoke() Servlet.service() for servlet [rest] in context with path [/operatorconsole_portlet] threw exception [Request processing failed; nested exception is com.firehunter.webapp.api.util.InvalidUserException: Invalid sid value found in request headers.] with root cause
Oct 27 15:17:03:322 ERROR [http-nio-80-exec-6, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/operatorconsole_portlet].[rest]] com.firehunter.webapp.api.util.InvalidUserException: Invalid sid value found in request headers.
Oct 27 15:17:03:323 ERROR [http-nio-80-exec-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/operatorconsole_portlet].[rest]] invoke() Servlet.service() for servlet [rest] in context with path [/operatorconsole_portlet] threw exception [Request processing failed; nested exception is com.firehunter.webapp.api.util.InvalidUserException: Invalid sid value found in request headers.] with root cause
Oct 27 15:17:03:323 ERROR [http-nio-80-exec-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/operatorconsole_portlet].[rest]] com.firehunter.webapp.api.util.InvalidUserException: Invalid sid value found in request headers.
Oct 27 15:17:32:809 ERROR [http-nio-80-exec-6, com.firehunter.ump.auth.NmsAuth] Unable to login for sso
Release : 20.3
Component : UIM - OPERATOR CONSOLE
Defect in 20.3 that is resolved in 20.3.1
After upgrading to 20.3.1, this issue is resolved.
UIM 20.3.1 patch can be downloaded from here:
https://support.broadcom.com/external/content/release-announcements/CA-Unified-Infrastructure-Management-Hotfix-Index/7233