Access Manager 3.1 SP2 Beta 1 Scenarios
7
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
4e
Click
Next
.
4f
Modify the
Text
and
Image
to fit your needs.
4g
Click
Finish
.
5
Update the Identity Server.
6
Make sure the Access Gateway has two protected resources (PR1 and PR2). Create them if
necessary.
7
Assign authentication contract C1 to protected resource PR1.
8
Assign authentication contract C2 to protected resource PR2.
9
Update the Access Gateway.
10
Access a page on protected resource PR1 from a client browser.
You should be prompted to authenticate.
11
Access a page on protected resource PR2 with the same browser session.
You should be prompted to authenticate again. Make sure to use the same user for both logins.
12
Refresh the page on protected resource PR2 at least once a minute over a time period greater
than 5 minutes.
13
Go back to the page on protected resource PR1.
Access should still be allowed. The user has not been inactive, so the activity has kept the
session to PR1 active.
14
Access the page on protected resource PR2 again.
15
Let the browser sit idle for a time period greater than 5 minutes but less than 10 minutes.
16
Refresh the page on protected resource PR2.
The page should refresh without prompting you to authenticate.
17
Access the page on protected resource P1.
You should be prompted to authenticate again. You have been idle longer than the contract’s
timeout limit.
2.1.4 Test Results
Activity on a protected resource with the same realm as other protected resources prevents
authentication timeout on the other protected resources.
Each protected resource can have a different authentication timeout.
2.1.5 Troubleshooting Tips
An authentication contract with an empty realm or a realm of
Any
allows activity from any
protected resource to prevent a timeout on a protected resource that uses that contract.
