I3:FeatureTest-Selector Support for Non-Auditing Cards

From OSIS Open Source Identity Systems

Jump to: navigation, search

   list help  copy  as XML  edit
Feature Test   Selector Support for Non-Auditing Cards
Test Type   Card Usage
Identifier   FTI3-iis-cardusage-m2  
Description   Tests selector's support for ClientPseudonym and it not supplying AppliesTo information for non-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   ClientPseudoym in RST with value D+HE7IgHDjQm61AGjrfW4xG4J/G9aXEP3leRNV6pwko= and no AppliesTo in RST  
Failure Criteria   ClientPseudoym not present, value different, or AppliesTo present  

Features Proven

Feature feature_type solution_role
Support for Non-Auditing Cards Information Card Identity Selector interop
  1. Open the result page for your solution and for this test.
  2. Import the "I3 Echo Non-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 ClientPseudoynm value displayed is D+HE7IgHDjQm61AGjrfW4xG4J/G9aXEP3leRNV6pwko= and the AppliesTo value displayed is "No AppliesTo in RST".
  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 ClientPseudoynm value displayed is iCDV30WYaD9mZcs70LTLxKBKjBjrn341nHJnG8ZEnCw= and the AppliesTo value displayed is "No AppliesTo in RST".
  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.