single sign on - SAML 2 Signature error in ADFS 2.0 -


in our sso scenario, using adfs 2.0 idp , shibboleth sp. sp-initiated sign-on. after configuring, when try establish communication between shibboleth , adfs 2.0(throw browser redirect), adfs 2.0 throwing below error.

the verification of saml message signature failed. message issuer: http://sampleserver/adfs/services/trust exception details: msis1015: server required signed saml authenticationrequest no signature present.

event id - 320 related event id - 364

> microsoft.identityserver.service.samlprotocol.samlprotocolsignatureverificationexception: > msis1015: server required signed saml authenticationrequest no > signature present.    @ > microsoft.identityserver.service.samlprotocol.samlprotocolservice.validatesignaturerequirements(samlmessage > samlmessage)    @ > microsoft.identityserver.service.samlprotocol.samlprotocolservice.issue(issuerequest > issuerequest)    @ > microsoft.identityserver.service.samlprotocol.samlprotocolservice.processrequest(message > requestmessage) 

we haven't used signature yet. have made signedsamlrequest false in adfs properties. signing of saml @ shibboleth disabled.

i not find information in microsoft site - apart generic guide sort of errors.

please advice on error.

i able find solution after lot analysis. shibboleth configuration issue. in application defaults section, entity id should unique application.

applicationdefaults signing="false" entityid="http://url of protected application " remote_user="eppn persistent-id targeted-id"

another variation of error happens when sigining set true. result in signature mismatch error in adfs.


Comments

Popular posts from this blog

java - Run spring boot application error: Cannot instantiate interface org.springframework.context.ApplicationListener -

reactjs - React router and this.props.children - how to pass state to this.props.children -

Excel VBA "Microsoft Windows Common Controls 6.0 (SP6)" Location Changes -