I4:FeatureTest-Selector Preserves MasterKey when Overwriting Card

From OSIS Open Source Identity Systems

list help  copy  as XML  edit

Feature Test	Selector Preserves MasterKey when Overwriting Card
Test Type	Card Usage
Identifier	FTR-iis-cardmgmt-4
Description	Tests that Selector retains the MasterKey and HashSalt when a card is overwritten by a card with the same CardID from a .crd file
Role tested	Information Card Identity Selector
Known Successful Reference Solution(s)	I4:CardSpace .NET Framework 3.5
Success Criteria	The card generates the same ClientPseudonym after being overwritten
Failure Criteria	ClientPseudonym changes after the card is overwritten

Features Proven

Feature	feature_type	solution_role
ClientPseudonym for Auditing Managed Card remains the same after overwriting card in Selector	Information Card Identity Selector	interop
Notify user on Card import if Card is already installed in Identity Selector	Information Card Identity Selector	usability

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. Select the "I3 Echo Auditing" card and preview the claims to be sent using the username "testclient" and password "testpassword".
   1. Record the PPID value being previewed. (It will be UPM-4UWF-FAH if the ISIP 1.5 algorithm is being used or DBK-G45T-NUQ if the ISIP 1.0 algorithm is being used.)
4. Submit the card.
   1. Record the ClientPseudonym value displayed. (It will be 9huBthvsZVc0bOENyKKzzuRrjoOWOyYGymtlRgHFp5w= if the ISIP 1.5 algorithm is being used or u/wthPNzyVKlLpQ9fFbvRxCzYYDcEasHMPUVn/kwuzg= if the ISIP 1.0 algorithm is being used.)
5. Now visit the site https://ipsts.federatedidentity.net/MgmtConsole/TestAccount.aspx?cardType=echoCard0 and click the icon to install the "Auditing" Echo STS card.
   1. The selector should display a warning along the lines of "A card with the same version exists. Importing will replace this card." This is OK. Proceed to import the card.
6. Visit https://relyingparty.federatedidentity.net/CardSelectorRP/login.aspx and click the icon to submit a card. Select the "Auditing" card and preview the claims to be sent using the username "testclient" and password "testpassword".
   1. Compare the PPID value being previewed to the value recorded earlier. It should be the same.
7. Submit the card.
   1. Compare the ClientPseudonym value displayed to the one you recorded earlier. It should be the same.
8. 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.
9. Add either four tilde ~~~~ signs or a text name into the "Tested by" parameter.
10. Update the Date Tested, Browser, and Operating System lines of the results page.