Yes, it was for educational purposes only. Regards
On Wed, Mar 23, 2016 at 11:47 PM, Kalle Korhonen <kalle.o.korho...@gmail.com > wrote: > I don't see a reason to do a plain servlet implementation if it's not for > educational reasons only. JAX-RS or even a Tapestry API would serve you > much better as an Oauth endpoint. > > Kalle > > On Wed, Mar 23, 2016 at 1:13 AM, abangkis <abang...@gmail.com> wrote: > > > Thanks Kalle. Yes, I've been following that. Turning the Jax-RS sample > to a > > servlet one, before try to migrate it to tapestry. I Guess my knowledge > on > > OAuth2, JAX-RS & Servlet isn't deep enough to quickly do it for now. I'll > > set aside a few weekends to learn more about it in the future :) > > > > > > On Wed, Mar 23, 2016 at 12:36 PM, Kalle Korhonen < > > kalle.o.korho...@gmail.com > > > wrote: > > > > > Adapting the code from Oltu's integration tests (e.g. see > > > > > > > > > https://github.com/apache/oltu/blob/trunk/oauth-2.0/integration-tests/src/test/java/org/apache/oltu/oauth2/integration/endpoints/AuthzEndpoint.java > > > ), > > > it should be relatively simple to implement Oauth authorization & > > resource > > > servers as JAX-RS endpoints with Tynamo's tapestry-resteasy ( > > > http://www.tynamo.org/tapestry-resteasy+guide/). > > Tynamo-federatedaccounts > > > can certainly be used as a a client to your own server with some > > > customization. It's not too difficult, but previous knowledge on basic > > > Oauth workflow and JAX-RS is required. I'd love to make this much > simpler > > > really but there are lots and lots of options how you want things to > > behave > > > so one size doesn't fit all. > > > > > > One of the more interesting things in authorization space I've been > > working > > > on lately is invoking an Oauth request with a third-party authorization > > > server from an Ember client, then validating the access token through > my > > > own service, federating it with a local account and finally returning > > JWTs > > > for sessionless *and* using the same tokens for authorizing websocket > > > connections. Phew. I may try to spin some parts of it off to an open > > source > > > library but not quite sure yet what exactly would make a good reusable > > > module. > > > > > > Kalle > > > > > > On Tue, Mar 22, 2016 at 6:39 PM, abangkis <abang...@gmail.com> wrote: > > > > > > > Hi all, thanks for the response. Yes, it's the server Implementation > :) > > > > > > > > I don't think i would integrate spring social, since I don't use > > spring. > > > > Been tinkering with the servlet implementation of OAuth2, turn out > the > > > > effort is greater than I previously think (probably because I don't > > > > understand OAuth2 that well). So i think I'm going to lower the > > priority > > > of > > > > using OAuth2 for now. > > > > > > > > Thanks everyone :) > > > > > > > > On Tue, Mar 22, 2016 at 10:46 PM, Prakash Manjeshwar < > > > > pvmanjesh...@gmail.com > > > > > wrote: > > > > > > > > > My OAuth know-how is very limited. Nevertheless, following links > > might > > > > > help... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://gist.github.com/sody/1324553/f4a12ce37f65b96b98c98921ab9caff7d6d5d037 > > > > > > > > > > > > > > > > > > > > > > > > > http://docs.spring.io/spring-social/docs/1.0.x/reference/html/implementing.html > > > > > > > > > > > > > > > > > > > > > > > > > http://docs.spring.io/spring-social/docs/1.0.x/reference/html/overview.html#table-spring-social-modules > > > > > > > > > > > > > > > > > > > > --- > > > > > Regards, > > > > > Prakash > > > > > > > > > > > > > > > On 22 March 2016 at 21:06, Thiago H de Paula Figueiredo < > > > > > thiag...@gmail.com> > > > > > wrote: > > > > > > > > > > > On Tue, 22 Mar 2016 12:27:59 -0300, Prakash Manjeshwar < > > > > > > pvmanjesh...@gmail.com> wrote: > > > > > > > > > > > > I think, original question was about an OAuth *server > > implementation > > > > *as > > > > > >> there was reference to Apache Oltu. > > > > > >> > > > > > > > > > > > > Oh, I'm sorry. I read the message too quickly and I didn't notice > > the > > > > > > "server" part. (facepalm). > > > > > > > > > > > > Thanks for the shout out to Oltu. I didn't know about it and it > > seems > > > > > > pretty interesting. It shouldn't be hard to integrate it into a > > > > Tapestry > > > > > > application. > > > > > > > > > > > > Is Tynamo not a client only solution ? > > > > > >> > > > > > > > > > > > > Yes. > > > > > > > > > > > > > > > > > > -- > > > > > > Thiago H. de Paula Figueiredo > > > > > > Tapestry, Java and Hibernate consultant and developer > > > > > > http://machina.com.br > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > http://www.mreunionlabs.net/ <http://www.mreunion-labs.net/> > > > > twitter : @mreunionlabs @abangkis > > > > page : https://plus.google.com/104168782385184990771 > > > > > > > > > > > > > > > -- > > http://www.mreunionlabs.net/ <http://www.mreunion-labs.net/> > > twitter : @mreunionlabs @abangkis > > page : https://plus.google.com/104168782385184990771 > > > -- http://www.mreunionlabs.net/ <http://www.mreunion-labs.net/> twitter : @mreunionlabs @abangkis page : https://plus.google.com/104168782385184990771
