As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For users of CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files

Overview

The samlSubjectConfirmations (Holder of Key (HOK), bearer, sender-vouches) are the method used to confirm the identity of the requester. These methods should be implemented at the adapter level and not present in the reference adapter. These tests are designed to verify the samlSubjectConfirmations using mock adapter and confirmed (success or fail) if the expected elements are missing from the request.

Test Detail

The Document Query (DQ) in Passthrough mode are running with JMX call script to set the CONNECT application to Passthrough without application restart and the test cases set up the expected samlSubjectConfirmations (HOK, bearer, sender-vouches) and response with registryError (Failure) if the expected elements are missing.

Update config (DQ)
Setup MockAdapter (samlSubjectConfirmations) to expected element.
Send DQ Request (with/without) samlSubjectConfirmations and verify expected result.

SAMLSubjectConfirmationTestSuite

HOK

MockAdapter expected samlSubjectConfirmations (HOK)

Update config
Document Query
- Assert DocumentId
- Expected status (success)

HOK-Bear-SenderVouches

MockAdapter expected samlSubjectConfirmations (HOK, Bearer, Sender-Vouches)

Update config
Document Query (samlSubjectConfirmations: Bearer, Sender-Vouches)
- Assert DocumentId
- Expected status (success)

HOK-SenderVouches

MockAdapter expected samlSubjectConfirmations (HOK, Sender-Vouches)

Update config
Document Query (samlSubjectConfirmations: Sender-Vouches)
- Assert DocumentId
- Expected status (success)

HOK-Missing-SenderVouches