[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: MSIS1016: Relying party trust 'myapp-saml' indicates that authentication requests sent by this relying party will be signed but no signature present.
Hello, I’m trying to get a new SAML integration set up as a service provider. The identity provider is getting the following error logged with my app. My app is the demo app found here:
https://github.com/onelogin/php-saml I’ve been reading through the docs here (https://www.oasis-open.org/standards#samlv2.0) , but am not very familiar
with SAML as this is my first attempt at an integration. Any help deciphering this error would be greatly appreciated. I can go to the demo, it’ll redirect the request to the identity provider, lets me log in, and then I’m taken back to my site with a response. And though it's routing, it's giving this error: The verification of the SAML message signature failed. Message issuer: myapp-saml Exception details: MSIS1016: Relying party trust 'myapp-saml' indicates that authentication requests sent by this relying party will be signed but no signature present. This request failed. Request: <samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="ONELOGIN64d0c596641a429c84feddd40e9d872ac187c769" Version="2.0" IssueInstant="2013-06-18T15:20:44Z" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" AssertionConsumerServiceURL="https://serviceprovider.com/php-saml-master/demo/consume.php"> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">myapp-saml</saml:Issuer> <samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" AllowCreate="true"></samlp:NameIDPolicy> <samlp:RequestedAuthnContext Comparison="exact"> <saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport</saml:AuthnContextClassRef> </samlp:RequestedAuthnContext> </samlp:AuthnRequest> Response: <?xml version="1.0"?> <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="_83dcb147-999c-4680-b563-79515a2cdbee" Version="2.0" IssueInstant="2013-06-18T15:22:00.312Z" Destination="https://serviceprovider.com/php-saml-master/demo/consume.php"
Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified" InResponseTo="ONELOGIN141dd7c5432d88e8b4b05fd9e2e02859b78f4c30"> <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">http://identityprovider.com/adfs/services/trust</Issuer> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <ds:Reference URI="#_83dcb147-999c-4680-b563-79515a2cdbee"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>taz2UYotrb35GvMZaj66M/Ay9YU=</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue><!-- Signature removed --></ds:SignatureValue> <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"> <ds:X509Data> <ds:X509Certificate><!-- 509 certificate removed --></ds:X509Certificate> </ds:X509Data> </KeyInfo> </ds:Signature> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Responder"/> </samlp:Status> </samlp:Response> Thanks, Tim __________________________________________ D: (410) 962-6434
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]