Thanks for the clarification Antonio, so you're right, if it's a totally different specification then it deserves a proper "root" module :-) Regards, Tommaso
2013/1/16 Antonio Sanso <[email protected]> > Hi Tommaso, > > yes you are right. OpenId connect is based on OAuth 2.0. > But differently from the other spec e.g. jwt is a totally different > specification not even under the IETF umbrella. > > Hence why I was thinking to separate... > > Regards > > Antonio > > On Jan 16, 2013, at 11:45 AM, Tommaso Teofili wrote: > > > Hi Antonio, > > > > if OpenId Connect is based on OAuth 2.0 maybe it'd make more sense to > have > > the related module under oatuh-2.0 as well. > > What do you think? > > > > Tommaso > > > > > > 2013/1/16 Antonio Sanso <[email protected]> > > > >> Hi *, > >> > >> as mentioned previously it would be nice to start some work around > OpenId > >> Connect, see AMBER-24 [0]. > >> > >> Now, Open Id Connect is built on top of OAuth 2.0 and also use a new > part > >> of the specification, namely JSON Web Token, see AMBER-63 [1]. > >> > >> Now I'd propose to extend the structure of the project and add jwt under > >> the oauth 2 part of the project as a module namely under > >> > >> /amber/trunk/oauth-2.0/jwt > >> > >> and put openid connect one level above (outside the oauth 2 area) e.g. > >> > >> /amber/trunk/openid-connect > >> > >> WDYT? > >> > >> Regards > >> > >> Antonio > >> > >> > >> [0] https://issues.apache.org/jira/browse/AMBER-24 > >> [1] https://issues.apache.org/jira/browse/AMBER-63 > >> > >
