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 (HOK, bearer, sender-vouches) are the method used to confirm the identity of the requester; these method should be implement at the adapter level and not present in the reference adapter. The Test designed to verify the samlSubjectConfirmations using mock adapter and confirmed (success, fail) if the expected element are missing from the request.
Test Detail
The DQ (Passthrought) are running with JMX call script to set the CONNECT application to Passthrough without application restart, and the Test Cases setup the expected samlSubjectConfirmations (HOK, bearer, sender-vouches) and response with registryError (Failure) if the expected elements are missing.
Update config (DQ)
Setup MockAdapter (samlSubjectConfirmations) expected element
Send DQ Request (with/with) samlSubjectConfirmations and verify expected result.
SAMLSubjectConfirmationTestSuite
HOK
MockAdapter expected samlSubjectConfirmations (HOK)
update config
Document Query
Assert DocumentId
Expect status (success)
HOK-Bear-SenderVouches
MockAdapter expected samlSubjectConfirmations (HOK, Bear, Sender Voucher)
update config
Document Query (samlSubjectConfirmations: Bear, Sender Voucher)
Assert DocumentId
Expect status (success)
HOK-SenderVouches
MockAdapter expected samlSubjectConfirmations (HOK, Sender Voucher)
update config
Document Query (samlSubjectConfirmations: Sender Voucher)
Assert DocumentId
Expect status (success)
HOK-Missing-SenderVouches
MockAdapter expected samlSubjectConfirmations (HOK, Sender Voucher)
update config
Document Query
Assert status (Failure)
MockDQAdapter
Success (found expected samlSubjectConfirmations)
Failure (missing expected samlSubjectConfirmation)