EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB442578: Error "Cannot sign outgoing message as no signing credential is set in the context" is received when accessing mstrWeb page after configuring SAML authentication


Yuxia Zhang

Quality Engineer • MicroStrategy


This article explains a possible cause for error "Cannot sign outgoing message as no signing credential is set in the context" in an environment with SAML setup.

SYMPTOM:
Error "Cannot sign outgoing message as no signing credential is set in the context" is received when accessing mstrWeb page after configuring SAML authentication.

ka02R000000bt68QAA_0EM44000000RfP6.png

In the Tomcat localhost.log, the below entries are present.
 


SEVERE [http-nio-8080-exec-10] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [mstrWeb] in context with path [/Strategy1] threw exception
 java.lang.IllegalArgumentException: Cannot sign outgoing message as no signing credential is set in the context
	at org.springframework.util.Assert.notNull(Assert.java:134)
	at org.springframework.security.saml.processor.SAMLProcessorImpl.sendMessage(SAMLProcessorImpl.java:219)
	at org.springframework.security.saml.processor.SAMLProcessorImpl.sendMessage(SAMLProcessorImpl.java:192)
	at org.springframework.security.saml.websso.AbstractProfileBase.sendMessage(AbstractProfileBase.java:148)
	at org.springframework.security.saml.websso.WebSSOProfileImpl.sendAuthenticationRequest(WebSSOProfileImpl.java:107)
	at org.springframework.security.saml.SAMLEntryPoint.initializeSSO(SAMLEntryPoint.java:225)
	at org.springframework.security.saml.SAMLEntryPoint.commence(SAMLEntryPoint.java:152)
	at com.Strategy.auth.saml.SAMLEntryPointWrapper.commence(SAMLEntryPointWrapper.java:45)
	at org.springframework.security.web.access.ExceptionTranslationFilter.sendStartAuthentication(ExceptionTranslationFilter.java:203)
	at org.springframework.security.web.access.ExceptionTranslationFilter.handleSpringSecurityException(ExceptionTranslationFilter.java:177)
	at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:133)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
	...
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)

CAUSE:
A possible cause is that the SP Entity ID and IDP Entity ID are identical. This can be verified by checking the entityID field in SPMetadata.xml and IDPMetadata.xml.
ACTION:
Use different Entity IDs for SP and IDP. 
  KB442578


Comment

0 comments

Details

Knowledge Article

Published:

January 8, 2019

Last Updated:

July 8, 2020