Project

General

Profile

Bug #8164

artifact resolve success message on error

Added by Frédéric Péters (de retour le 10/10) about 7 years ago. Updated over 3 years ago.

Status:
Nouveau
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03 September 2015
Due date:
% Done:

0%

Estimated time:
Patch proposed:
No
Planning:
No

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


Related issues

Related to Lasso - Bug #8166: Signature errors during lasso_login_process_request_msg are later ignored by lasso_login_build_response_msgNouveau03 September 2015

Actions

History

#1

Updated by Benjamin Dauvergne about 7 years ago

  • Target version set to future
#2

Updated by Benjamin Dauvergne about 7 years ago

  • Related to Bug #8166: Signature errors during lasso_login_process_request_msg are later ignored by lasso_login_build_response_msg added
#3

Updated by Benjamin Dauvergne about 7 years ago

  • Status changed from Nouveau to Fermé
#4

Updated by Benjamin Dauvergne over 3 years ago

  • Status changed from Fermé to Nouveau

Also available in: Atom PDF