I3:FeatureTest-Selector Support for Auditing Cards

From OSIS Open Source Identity Systems

list help  copy  as XML  edit

Feature Test	Selector Support for Auditing Cards
Test Type	Card Usage
Identifier	FTI3-iis-cardusage-m4
Description	Tests selector's support for AppliesTo and ClientPseudonym information for auditing cards. Also tests ClientPseudonym generation algorithm.
Role tested	Information Card Identity Selector
Known Successful Reference Solution(s)	I3:CardSpace .NET Framework 3.5
Success Criteria	AppliesTo and ClientPseudoyum values both present in RST with values as below
Failure Criteria	AppliesTo or ClientPseudoym not present or values different

Features Proven

Feature	feature_type	solution_role
Support for Auditing Cards	Information Card Identity Selector	interop

1. Open the result page for your solution and for this test.
2. Import the "I3 Echo Auditing" card from the file Image:I3 echo sts cards.crds using the password "i3_echo_sts_cards".
3. Visit https://relyingparty.federatedidentity.net/CardSelectorRP/login.aspx and click the icon to submit a card. Submit the card using the username "testclient" and password "testpassword".
   1. Verify that the AppliesTo value displayed contains [Address: https://relyingparty.federatedidentity.net/CardSelectorRP/login.aspx] and the certificate information for the four certificates in the chain and that the ClientPseudoynm value displayed is u/wthPNzyVKlLpQ9fFbvRxCzYYDcEasHMPUVn/kwuzg=.
4. If the selector supports no-SSL, also visit http://relyingparty.federatedidentity.net/CardSelectorRP/login.aspx and click the icon to submit a card. Submit the card using the username "testclient" and password "testpassword".
   1. Verify that the AppliesTo value displayed is Address: http://relyingparty.federatedidentity.net/CardSelectorRP/login.aspx and that the ClientPseudoynm value displayed is qQffn/VgCNpgKVLmsCpMRvNHocxTTnBPTkRAEDscQ5U=.
5. Set outcome:
   1. If the success criteria was met, set the outcome to "Works".
   2. If the test failed, set the outcome to "Failed" and enter information about the failure in the Notes section.
   3. If other issues occurred set the result to "Issues" and describe them in the Notes section.
6. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
7. Update the Date Tested, Browser, and Operating System lines of the results page.