[OIDFSC] Native application SSO Working Group
tonynad at microsoft.com
Wed Jul 3 21:42:09 UTC 2013
This is a real crappy name, as its not SSO, it's a "token delegation agent" (so proposal is to handle both authentication and authorization). Question is does it belong here or at IETF, if the dynamic registration fits in IETF why wouldn't this ?
From: openid-specs-bounces at lists.openid.net [mailto:openid-specs-bounces at lists.openid.net] On Behalf Of Mike Jones
Sent: Wednesday, July 3, 2013 2:26 PM
To: John Bradley; specs-council at openid.net
Cc: ashishjain at vmware.com; Paul Madsen; openid-board at lists.openid.net; openid-specs at lists.openid.net
Subject: RE: [OIDFSC] Native application SSO Working Group
This proposed charter did not incorporate any of the proposed improvements and clarifications that I circulated to the authors - not even the spelling corrections or the (I believe necessary) statement that "This specification will not make breaking changes to OpenID Connect 1.0".
My proposed version is attached. I would appreciate it you would resubmit the charter with these corrections incorporated. After that, I will support the formation of the working group.
From: openid-specs-council-bounces at lists.openid.net [mailto:openid-specs-council-bounces at lists.openid.net] On Behalf Of John Bradley
Sent: Sunday, June 30, 2013 5:35 PM
To: specs-council at openid.net
Cc: ashishjain at vmware.com; Paul Madsen; Chuck Mortimore; openid-specs at lists.openid.net; Nat Sakimura; matake at gmail; openid-board at lists.openid.net
Subject: [OIDFSC] Native application SSO Working Group
The enclosed Work Group Charter is being sent to the Specs Council for review in anticipation of chartering the Group.
It is best have this activity under the foundation IPR as soon as possible.
More information about the specs