Destination TimeIn

["Mishra, Prateek" <pmishra@netegrity.com>]

I am sending a short write-up describing the time
in notion. As suggested during the con-call, I have
focussed on the user's session experience as opposed
to any particular mechanism.


- prateek
------
Attachments are virus free!

This message has been scanned for viruses at the originating end by
Nemx Anti-Virus for MS Exchange Server/IMC
	http://www.nemx.com/products/antivirus

  

ISSUE:[UC-3-9:Destination-Time-In]

In this scenario, a user has traveled from the source site (site of initial login) to some destination site. The source site has set a maximum idle-time limit for the user session, based on user activity at the source or destination site. The user stays at the destination site for a period longer than the source site idle-time limit; and at that point the user returns to the source site. We do not wish to
have the user time-out at the source site and be re-challenged for authentication; instead, the user should continue to enjoy the original session which would somehow be cognizant of user activity at the destination site.

Candidate Requirement:

[CR-3-9:Destination-TimeIn]
SAML shall support destination system time-in.



Possible Resolutions:

1. Add this scenario and requirement to SAML.
2. Do not add this scenario or requirement to SAML.