I4:FeatureTest-Selector Preserves MasterKey when Updating Auditing Card

From OSIS Open Source Identity Systems
Revision as of 11:35, 31 August 2008 by Mike.Jones (Talk | contribs) (FeatureTest-Selector Preserves MasterKey when Updating Auditing Card)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-Selector Preserves MasterKey when Updating Auditing Card}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:Selector Preserves MasterKey when Updating Auditing Card|{{#if:{{#var:DtArticleSortKey}}||}}}}{{#ifeq:{{#var:header}}|no||

{{#ifeq:no|no||
{{#if:{{#var:refs}}|[[{{#var:page}}|no_ref's]]|[[Special:Call/DT Article show Refs,page={{#var:page}},refs=yes|ref's]]}}}} {{#if:{{#var:DtArticleSortKey}}|({{#var:DtArticleSortKey}})}}    list help  [[Special:Call/DT Article copy,cat=FeatureTest,from={{#var:page}},namespace=I4|copy]]  [[Special:Call/DT Articles list XML,type=FeatureTest,title={{#var:page}},namespace=I4|as XML]]  edit
}}
{{#if:|Feature Test |Feature Test }}   Selector Preserves MasterKey when Updating Auditing Card
Test Type   bgcolor={{{color}}}}}|Card Usage
Identifier   bgcolor={{{color}}}}}|FTR-iis-cardmgmt-5  
Description   bgcolor={{{color}}}}}|Tests that Selector retains the MasterKey when a card is overwritten by a new version of the card  
Role tested   bgcolor={{{color}}}}}|Information Card Identity Selector  
Known Successful Reference Solution(s)   bgcolor={{{color}}}}}|{{ #if: CardSpace .NET Framework 3.5 |
I4:CardSpace .NET Framework 3.5}}{{ #if: |
[[I4:]]}} {{ #if: |
}} {{ #if: |
}}  
Success Criteria   bgcolor={{{color}}}}}|The card generates the same ClientPseudonym after being overwritten  
Failure Criteria   bgcolor={{{color}}}}}|ClientPseudonym changes after the card is overwritten  

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=I4
 |linksto=I4:FeatureTest-Selector Preserves MasterKey when Updating Auditing Card
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-Selector Preserves MasterKey when Updating Auditing Card/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

  1. Open the result page for your solution and for this test.
  2. Import the "I3 Echo Auditing" card from the file File: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=echoCard1 and click the icon to install the "Auditing, (card version = 2)" Echo STS card.
    1. The selector should display a warning along the lines of "An older version of the same card 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 v2" 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.