I4:FeatureTest-RP Acceptance of Tokens Within Reasonable Validity Windows

From OSIS Open Source Identity Systems
Jump to: navigation, search

{{#vardefine:page|{{#if:{{#var:page}}|{{#var:page}}|FeatureTest-RP Acceptance of Tokens Within Reasonable Validity Windows}}}}{{#vardefine:nr|{{#if:{{#var:nr}}|{{#expr:{{#var:nr}}+1}}|1}}}}{{#vardefine:url|{{#replace:{{#var:page}}| |_}}}}{{#if:RP Acceptance of Tokens Within Reasonable Validity Windows|{{#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 }}   RP Acceptance of Tokens Within Reasonable Validity Windows
Test Type   bgcolor={{{color}}}}}|Token Validation
Identifier   bgcolor={{{color}}}}}|FTR-irp-tokenval-2  
Description   bgcolor={{{color}}}}}|Tests that a Relying Party can accept tokens that aren't exactly perfectly synchronized, but which are close enough in time to have the difference attributed to clock drift. Note in this case we are altering the token timestamp by a very small amount -- 5 seconds.  
Role tested   bgcolor={{{color}}}}}|Information Card Relying Party  
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}}}}}|Relying party accepts token  
Failure Criteria   bgcolor={{{color}}}}}|Relying party crashes or errors out  

Features Proven

{{#dpl:debug=1

 |resultsheader=\n
 |noresultsheader= {|\n|bgcolor=#eeeeee|No matching Feature found.\n|}\n
 |category=Feature
 |namespace=I4
 |linksto=I4:FeatureTest-RP Acceptance of Tokens Within Reasonable Validity Windows
 |nottitlematch = Feature.edit
 |include={Feature}.viewfromtest
 |includematch=/FeatureTest-RP Acceptance of Tokens Within Reasonable Validity Windows/s
 |table=class=sortable,-,Feature,feature_type,solution_role

}}

Instructions

Instructions

  1. Open the result page for the Solution being tested with this FeatureTest.
  2. If you don't already have it, import the test card from the file File:I4-stsmunge.crd into the Selector being tested.
  3. Open the relying party site
  4. Invoke the selector and select the "I4 STS Munge Tests" Card
  5. When prompted for the username, type "soon" as the username (password doesn't matter)
    1. If you forget what to type, you can open the IdP privacy policy for a reminder
    2. Note success/failure
  6. Return to the Relying Party
  7. Invoke the selector again and select the "I4 STS Munge Tests" Card
  8. When prompted for username, type "recent" as the username
    1. Note Success/Failure
  9. Set outcome:
    1. If both tokens were accepted by the relying party, set outcome to "Works".
    2. If either token was rejected by the relying party, set outcome to "Failed".
    3. If other issues occurred set the result to "Issues" and describe them in the Notes section.
  10. Enter either four tilde ~~~~ signs or your name into the "testedby" parameter.
  11. Update the date tested, operating systems, and tested solutions parameters of the results page.