On 21/04/2010 19:18, Paul Lindner wrote: > Ditto here. Apache Shindig uses OAuth extensively and we would like to > upgrade it to OAuth 2.0. The current stable java oauth library is okay, > but does not have an active developer community, and isn't even > published to maven central.
Both of those we can fix. > I just had a peek at Amber, looks fairly decent. I can help move this > to Apache incubating if people are interested. This also sounds promising. p > On Wed, Apr 21, 2010 at 4:49 AM, Simone Gianni <simo...@apache.org > <mailto:simo...@apache.org>> wrote: > > Hi Pid, > I'm also interested in developing a Java library for OAuth 2. There > is an Apache Lab (labs.apache.org <http://labs.apache.org> , lab > named Amber) working on an OAuth 1 Java API, it could (will) > eventually move to Incubator if we manage to get enough momentum. > > It would be nice to have a Java API that integrates with existing > systems, like JAAS and Spring Security (formerly known as Acegi). > That would ease the migration for all the frameworks and existing > systems that already use those libraries. > > Simone > > 2010/4/15 Pid <p...@pidster.com <mailto:p...@pidster.com>> > > Hi all, > > I'm interested in working with other Java programmers to develop a > standardised API for OAuth 2.0. > > I have reviewed the recent archives, but don't see anything in > the way > of discussion on this topic. If anyone can point me to a > location where > it is being discussed I'd be grateful. > > > I think it would be good if the OAuth community was able to > agree a spec > and then for implementors to have something to focus their efforts > against, instead of produced many different and incompatible > libraries. > > There are obviously challenges in attempting this before the > v2.0 itself > is final, but perhaps the effort will inform the overall debate. > > > The different Java implementations of OAuth version 1.0 each have > varying features and levels of complexity. Most implementations > focus > on the client component and don't provide server components at all. > I'd like to improve on that in a Java API. > > Some ideas I have include specifying that, in addition to > programmatical > configuration, an implementation should allow ServiceLoader and XML > based configurations, and perhaps even an Annotation based config. > > > I'd like to hear from anyone who'd be interested in combining > efforts, > Java programmer or not. > > > Cheers, > > > Pid > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org <mailto:OAuth@ietf.org> > https://www.ietf.org/mailman/listinfo/oauth > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org <mailto:OAuth@ietf.org> > https://www.ietf.org/mailman/listinfo/oauth > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
