Bug #8164
artifact resolve success message on error
Début:
03 septembre 2015
Echéance:
% réalisé:
0%
Temps estimé:
Patch proposed:
Non
Planning:
Non
Description
I did SSO from a service provider whose keys didn't match the metadata known to authentic and got this artifact response:
<samplp:ArtifactResponse><samlp:Status><samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/></samlp:Status></samlp:ArtifactResponse>
Authentic logs:
admin (295206) 3613fe92 INFO authentic2.idp.saml.return_login_response: sending Artifact to assertionConsumer 'https://meaux.test.au-quotidien.com/saml/assertionConsumerArtifact?SAMLart=AAQAAH9M%2F0OUCEt6U6vJwtHjxs6nZn2mNTUzQ0U1QzM4RTY1RTUyQzU5QUQ%3D' admin (295206) 3613fe92 INFO authentic2.idp.saml.finish_sso: sso treatment ended, send response - ecb53959 INFO authentic2.idp.saml.artifact: soap call received - ecb53959 ERROR authentic2.idp.saml.artifact: signature error for <lasso.DsSignatureVerificationFailedError(-111): Failed to verify signature.>: https://meaux.test.au-quotidien.com/saml/metadata - ecb53959 INFO authentic2.idp.saml.artifact: treatment ended, return answer
Demandes liées
Historique
Mis à jour par Benjamin Dauvergne il y a plus de 8 ans
- Lié à Bug #8166: Signature errors during lasso_login_process_request_msg are later ignored by lasso_login_build_response_msg ajouté