Signature validation is done using the Signed Xml class of the Microsoft . The Problem: Validating the digital signature contained in the SAML Assertion fails. I also need to open a case at F5 because of this problem. Message in Log is the following: Apr 11 f5-01 err tmm1: 014d0002:3: 35f9ae14: SSOv2 Digest from SAML message is invalid Apr 11 f5-01 err tmm1: 014d0002:3: 35f9ae14: SSOv2 Error(12) enveloped signature verification failed Apr 11 f5-01 err tmm1: 014d0002:3: 35f9ae14: SSOv2 Error(12) Signature verification failed for SAML Authentication Request Apr 11 f5-01 err tmm1: 014d0002:3: 35f9ae14: SSOv2 Error validating Authn Request Message.
From the log file: that is included in the SAML Response message. Status: urn:oasis:names:tc: SAML:2.0:status: Requester The problem has been solved by replacing the signing certificate in F5 APM.
Check if latest version of SAP Crypto lib is installed. Validate Signature Requirements(Saml Message saml Message)In SAML2 transaction, "Trusted Providers" tab, select your trusted IDP, choose tab "Signature and Encryption".
I assume this is because Liferay doesn't have enough information to know who I have authenticated as.I am having some issues getting the SAML portlet provided with Liferay 6.1EE to work with our existing Id P.First question: where is the official documentation for this portlet?Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed.If you received this in error, please contact the sender and delete the material from any computer.