I4:FeatureTest-RP Acceptance of Tokens Within Reasonable Validity Windows
From OSIS Open Source Identity Systems
|list help copy as XML edit|
|Feature Test||RP Acceptance of Tokens Within Reasonable Validity Windows|
|Test Type||Token Validation|
|Description||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||Information Card Relying Party|
|Known Successful Reference Solution(s)|
I4:CardSpace .NET Framework 3.5
|Success Criteria||Relying party accepts token|
|Failure Criteria||Relying party crashes or errors out|
|Provides Validity Window for token times to allow for imperfect Clock Synchronization||Information Card Relying Party Features||condition|
- Open the result page for the Solution being tested with this FeatureTest.
- If you don't already have it, import the test card from the file File:I4-stsmunge.crd into the Selector being tested.
- Open the relying party site
- Invoke the selector and select the "I4 STS Munge Tests" Card
- When prompted for the username, type "soon" as the username (password doesn't matter)
- Note success/failure
- Return to the Relying Party
- Invoke the selector again and select the "I4 STS Munge Tests" Card
- When prompted for username, type "recent" as the username
- Note Success/Failure
- Set outcome:
- If both tokens were accepted by the relying party, set outcome to "Works".
- If either token was rejected by the relying party, set outcome to "Failed".
- If other issues occurred set the result to "Issues" and describe them in the Notes section.
- Enter either four tilde ~~~~ signs or your name into the "testedby" parameter.
- Update the date tested, operating systems, and tested solutions parameters of the results page.