atom feed28 messages in org.oasis-open.lists.security-servicesRe: [security-services] Use Cases
FromSent OnAttachments
Beach, Michael COct 23, 2003 12:49 pm.bin, .doc
John KempNov 24, 2003 1:58 pm 
Beach, Michael CNov 25, 2003 11:24 am 
Greg WhiteheadNov 25, 2003 11:50 am 
Beach, Michael CNov 25, 2003 12:24 pm 
Greg WhiteheadNov 25, 2003 12:32 pm 
John KempNov 26, 2003 6:20 am 
Scott CantorNov 26, 2003 8:22 am 
John KempNov 27, 2003 7:49 am 
Scott CantorNov 28, 2003 9:30 pm 
Conor P. CahillNov 29, 2003 2:14 am 
Conor P. CahillNov 29, 2003 2:25 am 
Conor P. CahillNov 29, 2003 2:27 am 
John KempNov 29, 2003 5:54 am 
Conor P. CahillNov 29, 2003 11:35 am 
Beach, Michael CNov 29, 2003 11:37 am 
John KempNov 29, 2003 11:52 am 
Beach, Michael CNov 29, 2003 11:59 am 
Beach, Michael CNov 29, 2003 12:03 pm 
Conor P. CahillNov 29, 2003 1:46 pm 
Conor P. CahillNov 29, 2003 2:59 pm 
Anthony NadalinNov 30, 2003 5:23 pm 
Conor P. CahillNov 30, 2003 7:18 pm 
Conor P. CahillDec 1, 2003 4:16 am 
Anthony NadalinDec 1, 2003 9:31 pm 
Conor P. CahillDec 2, 2003 4:38 am 
Anthony NadalinDec 3, 2003 4:36 am 
Conor P. CahillDec 3, 2003 4:54 am 
Subject:Re: [security-services] Use Cases
From:John Kemp (onez@bcn.net)
Date:Nov 24, 2003 1:58:26 pm
List:org.oasis-open.lists.security-services

Mike,

I only just noticed that your use-cases were all session-related. I apologize for not replying to this email earlier. You describe in your use-cases three separate ecosystems (for session usage) that all share an IdP. Each ecosystem may have its own idle timeout value set that does not impact the other ecosystems. Although I'm not finished with a solution proposal, my idea is basically that although you may have a single IdP (or authentication authority), responsible for authenticating users from all ecosystems, you might also have a separate *session* authority for each of the ecosystems. Thus the 20-minute and 1-hour timeout sessions would not cause any issues, as they would have been issued by separate session authorities. The session authorities would refer to an authentication authority (which could be the same one for all, or a different one for each) to provide authentication services.

Does that make sense?

- JohnK

On Thursday, Oct 23, 2003, at 15:51 US/Eastern, Beach, Michael C wrote:

As I agreed, I have attempted to some use cases that Boeing would like to see addressed.  We would implement the described functionality immediately if it were possible with our technology.  The use case descriptions are attached.

This could be considered a draft that may be refined after comments.

Mike Beach Associate Technical Fellow The Boeing Company (425) 865-4404

<CorporateUseCases.doc><smime.p7s>