In the new version (0.5_rev3) of the reference implementation the shown title is now "JavaScript disabled" instead of the more proper messages (that were used in previous version). This happens for…
According to D5.8.1b Interface Specification v1.2.3_rev5.doc: If the subordinate status code is included in the response, then the status message must be the one corresponding to the subordinate…
Our test team has discovered the following problem: For error messages returned from IdP, PEPS shows urn:oasis:names:tc:SAML:2.0:status:Responder as error number. Steps to reproduce (reference…
When an SAMLToken validation fails (e.g. when used keys and certificates do not match), an incorrect message is shown to user: Error generating SAMLToken instead of Error validating SAMLToken The…
In PEPS 0.4 (SAMLEngine 0.4), optional and mandatory attributes could have an empty value by setting the STORKStatusCode to STATUS_AVAILABLE and providing an empty list as the value for…
Our test team has discovered the following problem in the reference SP (e.g. running on http://peps.indra.es/SP/populateIndexPage): When the SP requests QAAL 0 or 5 or -5 the following type of error…
Our test team has discovered the following problem: Requesting invalid QAA levels (e.g. 0, 5, -5, ABC) produces the following error message when using AT-SPEPS: ERROR An error occurred while…
Our test team has discovered the following problem: If requesting only optional attributes and none of them is confirmed/submitted by the user, the following error is shown in PEPS 0.4 / SAMLEngine 0…
Our test team has discovered the following problem: In version 0.4 two error messages are displayed if requesting an invalid gender attribute (e.g. "X"). On the first page, the error message does not…