Title: SimpleSAML_Error_Error: UNHANDLEDEXCEPTION Last modified: August 21, 2016 --- # SimpleSAML_Error_Error: UNHANDLEDEXCEPTION * [renperez01](https://wordpress.org/support/users/renperez01/) * (@renperez01) * [12 years, 1 month ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/) * Hello Keith, * I need your help. I am trying to use your plug in for our Word Press to authenticate using ADFS but I keep getting an error. * Here is the error: * SimpleSAML_Error_Error: UNHANDLEDEXCEPTION Backtrace: 0 /home/wp_hsg4u2/mywebsite. com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php:180 (N/A) Caused by: SimpleSAML_Error_Exception: Cannot retrieve metadata for IdP ‘[http://mywebsite.com/adfs/services/trust’](http://mywebsite.com/adfs/services/trust’); because it isn’t a valid IdP for this SP. Backtrace: 2 /home/wp_hsg4u2/engineering. tunein.com/wp-content/plugins/saml-20-single-sign-on/saml/modules/saml/lib/Auth/ Source/SP.php:112 (sspmod_saml_Auth_Source_SP::getIdPMetadata) 1 /home/wp_hsg4u2/ engineering.tunein.com/wp-content/plugins/saml-20-single-sign-on/saml/modules/ saml/www/sp/saml2-acs.php:72 (require) 0 /home/wp_hsg4u2/engineering.tunein.com/ wp-content/plugins/saml-20-single-sign-on/saml/www/module.php:135 (N/A) * [https://wordpress.org/plugins/saml-20-single-sign-on/](https://wordpress.org/plugins/saml-20-single-sign-on/) Viewing 6 replies - 1 through 6 (of 6 total) * Thread Starter [renperez01](https://wordpress.org/support/users/renperez01/) * (@renperez01) * [12 years, 1 month ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833518) * This is what I have under general tab and identity provider: * Entity ID: [https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1](https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1) * [https://engineering.tunein.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1](https://engineering.tunein.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1) * When I added the url to our ADFS console, it did not give me any errors. I was able to add it successfully and test the site. * Do you have any insight on how I can resolve this error? Thanks! * Thread Starter [renperez01](https://wordpress.org/support/users/renperez01/) * (@renperez01) * [12 years, 1 month ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833535) * This is the error i am getting on ADFS: * Encountered error during federation passive request. * Additional Data * Protocol Name: Saml * Relying Party: [https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1](https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1) * Exception details: Microsoft.IdentityModel.Protocols.XmlSignature.SignatureVerificationFailedException: MSIS0038: SAML Message has wrong signature. Issuer: ‘[https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1’](https://mywebsite.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1’);. at Microsoft.IdentityServer.Protocols.Saml.Contract.SamlContractUtility.CreateSamlMessage( MSISSamlBindingMessage message) at Microsoft.IdentityServer.Web.Protocols.Saml. SamlProtocolManager.Issue(HttpSamlRequestMessage httpSamlRequestMessage, SecurityTokenElement onBehalfOf, String sessionState, String relayState, String& newSamlSession, String& samlpAuthenticationProvider, Boolean isUrlTranslationNeeded, WrappedHttpListenerContext context, Boolean isKmsiRequested) at Microsoft.IdentityServer.Web.Protocols.Saml. SamlProtocolHandler.RequestBearerToken(WrappedHttpListenerContext context, HttpSamlRequestMessage httpSamlRequest, SecurityTokenElement onBehalfOf, String relyingPartyIdentifier, Boolean isKmsiRequested, Boolean isApplicationProxyTokenRequired, String& samlpSessionState, String& samlpAuthenticationProvider) at Microsoft.IdentityServer.Web.Protocols. Saml.SamlProtocolHandler.BuildSignInResponseCoreWithSerializedToken(HttpSamlRequestMessage httpSamlRequest, WrappedHttpListenerContext context, String relyingPartyIdentifier, SecurityTokenElement signOnTokenElement, Boolean isKmsiRequested, Boolean isApplicationProxyTokenRequired) at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.BuildSignInResponseCoreWithSecurityToken( SamlSignInContext context, SecurityToken securityToken, SecurityToken deviceSecurityToken) at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.Process(ProtocolContext context) at Microsoft.IdentityServer.Web.PassiveProtocolListener.ProcessProtocolRequest( ProtocolContext protocolContext, PassiveProtocolHandler protocolHandler) at Microsoft. IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context) * Thread Starter [renperez01](https://wordpress.org/support/users/renperez01/) * (@renperez01) * [12 years, 1 month ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833596) * Updated with a new error on my ADFS. * The Federation Service encountered an error while processing the SAML authentication request. * Additional Data Exception details: Microsoft.IdentityModel.Protocols.XmlSignature. SignatureVerificationFailedException: MSIS0038: SAML Message has wrong signature. Issuer: ‘[https://myweb.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1’](https://myweb.com/wp-content/plugins/saml-20-single-sign-on/saml/www/module.php/saml/sp/metadata.php/1’);. at Microsoft.IdentityServer.Protocols.Saml.Contract.SamlContractUtility.CreateSamlMessage( MSISSamlBindingMessage message) at Microsoft.IdentityServer.Web.Protocols.Saml. SamlProtocolManager.Issue(HttpSamlRequestMessage httpSamlRequestMessage, SecurityTokenElement onBehalfOf, String sessionState, String relayState, String& newSamlSession, String& samlpAuthenticationProvider, Boolean isUrlTranslationNeeded, WrappedHttpListenerContext context, Boolean isKmsiRequested) * [infrai](https://wordpress.org/support/users/infrai/) * (@infrai) * [11 years, 6 months ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833881) * [@renperez01](https://wordpress.org/support/users/renperez01/) Hi , I have the same issue , did you find the solution ? * Cheers, * [Marco Schmoecker](https://wordpress.org/support/users/marcosf/) * (@marcosf) * [11 years, 4 months ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833883) * I’m experiencing the same error. Did you find a solution for this? Or whu this is happening? * Thank you! -Marco * Thread Starter [renperez01](https://wordpress.org/support/users/renperez01/) * (@renperez01) * [11 years, 4 months ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833884) * Hey Guys, * Unfortunately i did not find a resolution for this. I ended up using google for single sign on which works great! Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘SimpleSAML_Error_Error: UNHANDLEDEXCEPTION’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/saml-20-single-sign-on.svg) * [SAML 2.0 Single Sign-On](https://wordpress.org/plugins/saml-20-single-sign-on/) * [Frequently Asked Questions](https://wordpress.org/plugins/saml-20-single-sign-on/#faq) * [Support Threads](https://wordpress.org/support/plugin/saml-20-single-sign-on/) * [Active Topics](https://wordpress.org/support/plugin/saml-20-single-sign-on/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/saml-20-single-sign-on/unresolved/) * [Reviews](https://wordpress.org/support/plugin/saml-20-single-sign-on/reviews/) * 6 replies * 3 participants * Last reply from: [renperez01](https://wordpress.org/support/users/renperez01/) * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/simplesaml_error_error-unhandledexception/#post-4833884) * Status: not resolved