Subject: Message did not meet security requirements
Date: 2014-12-08 06:59:24
From: Ilya Frolov
Source: message-not-meet-security-requirements
----------------------------------------------------------------------


	Hi, we're having trouble with the Idp and SP handshake. We're getting a "Message did not meet security requirements" error after redirecting to the identity provider.

	Here are the error logs in the IdP server: http://pastebin.com/2VwTdY69 . It seems to suggest a signing error. Can you guys help me out?

	This is the SP metadata:

	<EntityDescriptor ID="84CCAA9F05EE4BA1B13F8943FDF1D320" entityID="http://test.test.biz/shibbolethservice.aspx">

	<SPSSODescriptor WantAssertionsSigned="true" AuthnRequestsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

	<KeyDescriptor use="signing">

	<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">

	<X509Data>

	<X509Certificate>CERTIFICATE</X509Certificate>

	</X509Data>

	</KeyInfo>

	</KeyDescriptor>

	<KeyDescriptor use="encryption">

	<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">

	<X509Data>

	<X509Certificate>CERTIFICATE</X509Certificate>

	</X509Data>

	</KeyInfo>

	</KeyDescriptor>

	<AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="http://test.test.biz/ShibbolethService.aspx" index="1" isDefault="true" />

	</SPSSODescriptor>

	</EntityDescriptor>

----------------------------------------------------------------------

Note: This question has been asked on the Q&A forum of Thang Dang's fraudulent ComponentPro brand
If you purchased anything from ComponentPro, you have been scammed. Contact the payment processor
who sold you the license and ask for your money back.

Back to ComponentPro Q&A Forum Index