Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-04-05 Thread Kris Selden
cide which registration options to offer the >>> client if they make such a grant type available in the future, and how it >>> will apply the security policies. IOW, those proposing such an extension in >>> the future will have to figure out how this should be handl

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-04-05 Thread matake, nov
ecase of response_type=token%20code ? >> >> I thought, in that usecase, token was for the client's client-side >> component, >> >> code was for the client's server-side component, and both of them have the >> >> same client_id. >> >> &g

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-04-05 Thread matake, nov
EH > > > -Original Message- > > From: nov matake [mailto:n...@matake.jp] > > Sent: Sunday, March 11, 2012 10:21 AM > > To: Eran Hammer > > Cc: nov matake; oauth@ietf.org WG > > Subject: Re: [OAUTH-WG] Clarification of "client application consisting

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-04-05 Thread Kristofor Selden
--- >>> From: nov matake [mailto:n...@matake.jp] >>> Sent: Sunday, March 11, 2012 10:21 AM >>> To: Eran Hammer >>> Cc: nov matake; oauth@ietf.org WG >>> Subject: Re: [OAUTH-WG] Clarification of "client application consisting of >>> multiple c

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-03-11 Thread nov matake
unday, March 11, 2012 10:21 AM >> To: Eran Hammer >> Cc: nov matake; oauth@ietf.org WG >> Subject: Re: [OAUTH-WG] Clarification of "client application consisting of >> multiple components" >> >> So what is the usecase of response_type=token%20code ? >

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-03-11 Thread Eran Hammer
t; rest of the spec's security requirements. > > > > EH > > > >> -Original Message- > >> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On > >> Behalf Of nov matake > >> Sent: Sunday, March 11, 2012 8:25 AM > >> To: oa

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-03-11 Thread nov matake
.@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf >> Of nov matake >> Sent: Sunday, March 11, 2012 8:25 AM >> To: oauth@ietf.org WG >> Subject: [OAUTH-WG] Clarification of "client application consisting of >> multiple >> components" >> >> Hi

Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-03-11 Thread Eran Hammer
etf.org] On Behalf > Of nov matake > Sent: Sunday, March 11, 2012 8:25 AM > To: oauth@ietf.org WG > Subject: [OAUTH-WG] Clarification of "client application consisting of > multiple > components" > > Hi, > > I just found this sentence in the latest draft. >

[OAUTH-WG] Clarification of "client application consisting of multiple components"

2012-03-11 Thread nov matake
Hi, I just found this sentence in the latest draft. Does it mean "an application consisting of server-side and client-side component (eg. foursquare iPhone app) MUST have separate client_id for each component" ? Or can I image something like Facebook is doing right now? (register each componen