As far as I understand the group's charter, the user shall login to the authz agent once and in turn use the respective identity across apps on the same device. I would call this SSO.
Am 17.07.2013 um 20:54 schrieb Chuck Mortimore <[email protected]>: > I disagree. The functional goal of this, at least from a user's > perspective, should be Single Sign-On. > > -cmort > > > On Wed, Jul 17, 2013 at 11:49 AM, Anthony Nadalin <[email protected]> > wrote: >> I would have been too young back in the 90s >> >> >> >> I don’t like SSO in the name as this is basically this is just a way to >> authorize an app to interact with one or more resource serves on your behalf >> >> >> >> From: Paul Madsen [mailto:[email protected]] >> Sent: Wednesday, July 17, 2013 11:39 AM >> To: Don Thibeau >> Cc: Anthony Nadalin; Mike Jones; John Bradley; [email protected]; John Ehrig >> >> >> Subject: Re: [OIDFSC] Native application SSO Working Group >> >> >> I am 99% confident that *our* beloved Tony was not part of the R&B group >> from Oakland, briefly popular in the 90s..... >> >> https://en.wikipedia.org/wiki/Tony!_Toni!_Ton%C3%A9! >> >> >> On 7/17/13 2:33 PM, Don Thibeau wrote: >> >> Paul >> >> >> >> I don't think "Tony Tony Tony" is a good name for a working group :) >> >> >> >> Don Thibeau >> >> The OpenID Foundation >> >> >> >> >> >> >> >> On Jul 17, 2013, at 2:30 PM, Paul Madsen wrote: >> >> >> >> >> Tony Tony Tony, how I've missed our time together >> >> The WG's mandate is to profile OIDC to enable an SSO model for native mobile >> applications. >> >> Can you suggest a better (concise & memorable) descriptor for a mail list >> identifier? >> >> paul >> >> On 7/17/13 2:17 PM, Anthony Nadalin wrote: >> >> That’s a totally useless name >> >> >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Paul Madsen >> Sent: Wednesday, July 17, 2013 10:59 AM >> To: Mike Jones >> Cc: John Bradley; [email protected]; John Ehrig; Don Thibeau >> Subject: Re: [OIDFSC] Native application SSO Working Group >> >> >> >> that list name is fine >> >> thanks >> >> On 7/17/13 1:51 PM, Mike Jones wrote: >> >> John, are you able to create the new mailing list at lists.openid.net or do >> we have to ask [email protected] for the list creation? >> >> >> >> Paul and other WG creators, what name do you want the list to have? >> openid-specs-native-sso? >> >> >> >> -- Mike >> >> >> >> From: Don Thibeau [mailto:[email protected]] >> Sent: Wednesday, July 17, 2013 5:03 AM >> To: Paul Madsen >> Cc: n-sakimura; John Ehrig; [email protected]; John Bradley; >> Mike Jones >> Subject: Re: [OIDFSC] Native application SSO Working Group >> >> >> >> John Ehrig can set up the web site space and the online Docusign process for >> IPR collection. If done right away it saves all concerned lots of time and >> hassle. >> >> >> >> >> >> Don Thibeau >> >> The OpenID Foundation >> >> >> >> >> >> >> >> On Jul 17, 2013, at 7:59 AM, Paul Madsen wrote: >> >> >> >> >> >> >> Thanks Nat, >> >> Don, can you direct me to whomever I should work with on the WG list & page >> logistics? >> >> Paul >> >> On 7/16/13 6:08 AM, n-sakimura wrote: >> >> The WG formation is deemed to be approved per section 4.2 of the OpenID >> Process Document v.1.5 of 2009. >> >> A new mailing list should be established promptly per section 4.3 of the >> above document. Also, a WG web pages should be set up at openid.net. You >> should also ask the secretary of the foundation to announce the first >> meeting of the WG, in which scope approval and the chairs selection should >> be done. >> >> Note: the first meeting can only be done after the WG has collected the IPR >> agreement from the participants, so it may not be as quick as you may wish, >> but it has to be done. BTW, NRI's agreement is already in as we have a >> blanket agreement like Google. >> >> Nat >> >> (2013/07/15 14:56), Paul Madsen wrote: >> >> >> >> >> Next steps? >> >> ----------- >> Paul Madsen >> Ping Identity >> >> Anthony Nadalin<[email protected]> wrote: >> >> >> >> >> >> I believe if you dig you will see that there is potential for IPR from both >> Apple and Facebook. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of n-sakimura >> Sent: Wednesday, July 3, 2013 10:20 PM >> To: [email protected] >> Subject: Re: [OIDFSC] Native application SSO Working Group >> >> Could you kindly spell it out? >> >> From what I have been hearing, Facebook was just using fast application >> switch, which is nothing more than Self-issued thing that we have, and iOS's >> native login support given to facebook, twitter, and Weibo. >> Perhaps you are thinking of something else. >> >> Of course, I could be complete wrong. I should probably read >> https://developers.facebook.com/docs/howtos/ios-6/ >> and >> >> http://developer.apple.com/library/ios/#documentation/Social/Reference/Social_Framework/_index.html#//apple_ref/doc/uid/TP40012233 >> >> >> as well. >> >> Having said that, if Apple's interface is not open, perhaps it is a task for >> an industry consortia like OpenID Foundation to go and ask Apple to open up >> the API for other IdPs as well. Do not know if they are going to listen, but >> still, it might be our duty to try. >> >> Nat >> >> (2013/07/04 7:30), Anthony Nadalin wrote: >> >> >> >> >> I also have a concern that we might be infringing on the Facebook SSO >> (iOS) IPR with this effort. >> >> >> >> >> -- >> Nat Sakimura ([email protected]) >> Nomura Research Institute, Ltd. >> Tel:+81-3-6274-1412 Fax:+81-3-6274-1547 >> >> PLEASE READ: >> The information contained in this e-mail is confidential and intended for >> the named recipient(s) only. >> If you are not an intended recipient of this e-mail, you are hereby notified >> that any review, dissemination, distribution or duplication of this message >> is strictly prohibited. If you have received this message in error, please >> notify the sender immediately and delete your copy from your system. >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> specs mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-specs > > _______________________________________________ > specs mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-specs
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
