Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 75459 invoked from network); 14 Aug 2010 12:08:35 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Aug 2010 12:08:35 -0000 Received: (qmail 24446 invoked by uid 500); 14 Aug 2010 12:08:35 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 24137 invoked by uid 500); 14 Aug 2010 12:08:33 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 24125 invoked by uid 99); 14 Aug 2010 12:08:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Aug 2010 12:08:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lukasz.moren@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Aug 2010 12:08:24 +0000 Received: by qyk2 with SMTP id 2so293054qyk.0 for ; Sat, 14 Aug 2010 05:08:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=l7d0udxC8vQvNilsN0TMJlGXJRBntOgJeHXiOdRcjQU=; b=jB6857ddeVJtGU5o9nUEFuoZMwwxgk/xsIxPBiaHanPNxIsBGmTyt3g/P2ANhMllRD /0fvOXPQdG4kEMBcp5jkoA4RQI4WiVjCDyOlp3/KikjuD71WATZC0N871+eAULOHQkem gAwPIdm+9soatKlEJmNTqAUzPBRMVpLjkbpgc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pV2vLFsD29gauO2lzHDt1QSmdKonNVaP58Bt5faGyB7xCE4xoiFhS2l5FX93wcsGjM 9PlIdeY7rg4YIrFIv6sR1mFisQaMRSf15NiaJBhEPNn32H7l9n27N6l0qMUnWOjA7r7w oX9ET5CKIrvVQzwCy4NSgDoNfiU4pGYwaugrc= MIME-Version: 1.0 Received: by 10.224.11.131 with SMTP id t3mr1848077qat.262.1281787682663; Sat, 14 Aug 2010 05:08:02 -0700 (PDT) Received: by 10.229.219.68 with HTTP; Sat, 14 Aug 2010 05:08:02 -0700 (PDT) In-Reply-To: References: <201007291539.39801.dkulp@apache.org> Date: Sat, 14 Aug 2010 13:08:02 +0100 Message-ID: Subject: Re: OAuth client and server demos From: =?ISO-8859-2?B?o3VrYXN6IE1vcmXx?= To: dev@cxf.apache.org Content-Type: multipart/alternative; boundary=000e0cd1f8c880ac5d048dc77385 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1f8c880ac5d048dc77385 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Hi Sergey, Thanks for feedback. More comments below. 2010/8/13 Sergey Beryozkin > Hi Lucasz > > 2010/8/13 =A3ukasz More=F1 > > > Hi Sergey, > > > > I've added some improvements to demo and protocol implementation. > > I hope this time build will be fine. > > > > > I've had no problems building this time. Thanks for sorting the build > issues > out. > The only minor hitch is that I had to add > ../../pom.xml > to both oauth client & server demo modules in order to build them. Not su= re > if I could've built them by running > 'mvn install' from samples directly (in distribution/target/.../samples) > given that we also have to use -Pspring3. Not a big issue - please rechec= k > just in case... > Yes, I think I need to add relativePath to pom. > > So I've started server and client web apps and run the demo easily. So it= 's > all nearly there, and IMHO the project is in a good shape, as far as GSOC > is > concerned. Hopefully you can continue on preparing it to the move to the > trunk :-) > > Here're some comments to the existing demo - see if you could do anything > till 16th, if not then it can be dealt with later on. > > I will try do to as much as possible till 16-th. There is still plenty to d= o as I see from your commnets and myself so missing things I will add later. > The client registration form requires a user to register a callback URI. > But > I understand that a callback URI is only provided by a client, when > requesting a temp/request token ? That said, requiring what I'd call a > 'connect' or "reply-to" URI registered during the (secure) client > registration process may help with enforcing that the actual callback URI > provided by the client *matches* the one provided at the registration, > using > a startsWith function. I've seen it in the Facebook docs and I also did > something similar in my own project - is this the idea ? > If yes - then please check it's a startsWith check that is used - but also consider making providing a callback URI optional at the client registratio= n time Yes, i used it for that reason. It can be jus passed with request token request. All current OAuth 1.0 servers I've seen need to preregister callback URI, and as you said they check if both uri matches. There is also possibility to pass 'oob' (out of band) value as callback URI which means has been established via other means, so then server use preregistered value. However I think this option is used in case of native apps. . > The other thing is that a client key is also generated. This is probably > correct but I'm wondering would it make sense to let the consumer registe= r > its own key but the authorization server to only generate the shared > secret. > Consumer might also want to optionally provide its description such as > "OAuth 1.0 client" as in the demo, etc. This might make it a bit simpler > for a client (i.e, it will only have to manage a shared secret). > Yes I think it makes sense. So far consumer key is just hash from application name and user who registers consumer. > In a client webapp a PLAINTEXT option is offered - is it OAuth 2.0 like > thing where HTTPS is assumed ? I'd just consider removing this option and > have only hmac-sha1 left. > I think it's something similar, however there is no signatures in OAuth 2.0 and access_token is assumed to be short lived, ideally one per request, issuing new tokens is done by refresh_token parameter. > This is probably it so far. I'm not very excited about JSPs being used in > the demo :-) but I guess it is not too bad and shows something that many > people would consider doing in practice. > I was not sure about using JSP's neither:), but I wanted to show basically how oauth could be added to existing apps and hadn't other idea how to replace them. > > Overall it is a really good effort toward helping CXF users to > start/experiment with OAuth. > Cheers, Lukasz > > Thanks > > Sergey > > > Cheers, > > Lukasz > > > > 2010/8/13 Sergey Beryozkin > > > > > Hi =A3ukasz > > > > > > I can see the merges flowing :-), I'll be reviewing your work tonight= ; > > > > > > to the list : we've exchanged few private emails to do with build > issues > > I > > > was encountering and =A3ukasz > > > addressed them fast; we also agreed that for the initial phase makin= g > a > > > demo easy to understand and build upon was the main goal... > > > > > > cheers, Sergey > > > > > > 2010/8/5 Sergey Beryozkin > > > > > > > Hi =A3ukasz > > > > > > > > can you please fix checkstyle errors in the demo... > > > > Re the callback uri : I think one of the providers on the server is > > > > configured with the callback URI > > > > > > > > thanks, Sergey > > > > > > > > > > > > 2010/8/2 =A3ukasz More=F1 > > > > > > > > > > > > >> > Please update the demo so that the consume > > > >> > > > >> registers itself, plus supplies a callback itself with a request > token > > > >> > request > > > >> > > > >> > > > >> callback url is passed in this request, however this request is do= ne > > in > > > >> backend through URLConnection so it's not visible at UI. > > > >> > > > >> Cheers, Lukasz > > > >> > > > >> W dniu 2 sierpnia 2010 13:36 u=BFytkownik =A3ukasz More=F1 < > > > >> lukasz.moren@gmail.com > > > >> > napisa=B3: > > > >> > > > >> > Hi, > > > >> > I've committed changes I've made: > > > >> > - added possibility to register new OAuth client applications at > > OAuth > > > >> > server > > > >> > - OAuth demos moved to distribution\src\main\samples\ > > > >> > - added README to OAuth demos > > > >> > - fixes in pom.xml files > > > >> > > > > >> > - fix the checkstyle errors and move the demo to the > > > >> > > > > >> > ""distribution/src/main/release/samples/"" area and also add > Readme; > > > >> after > > > >> > > > > >> > building the distribution (mvn install in trunk/distribution) yo= u > > can > > > >> >> easily > > > >> > > > > >> > verify the demo can be run by locating in the target. > > > >> > > > > >> > > > > >> > fixed that, and added readme > > > >> > > > > >> > > > > >> >> - add the oauth dependency in the parent pom so that the rs/oau= th > > > >> module > > > >> >> can > > > >> > > > > >> > depend on it without specifying a version and have the demo clie= nt > > > >> module > > > >> > > > > >> > depending on rt/rs/oauth module instead (similarly to the server > > one) > > > >> > > > > >> > > > > >> > done, hovewer demo client don't need to depend on rt/rs/oauth as > it > > > >> doesn't > > > >> > use cxf functionality, just on oauth libraries > > > >> > > > > >> > > > > >> >> - during the main build please use the Spring version CXF depen= ds > > > upon > > > >> and > > > >> > > > > >> > use its -Pspring3 profile to build for the deployment into GAE > > > >> > > > > >> > > > > >> > changed, both client and server demos needs to be build with > > -Pspring3 > > > >> for > > > >> > local jetty run and GAE as well. > > > >> > Otherwise I would need use different spring config files for > spring > > > 2.5 > > > >> and > > > >> > 3.0.x > > > >> > > > > >> > Cheers, Lukasz > > > >> > > > > >> > W dniu 29 lipca 2010 21:15 u=BFytkownik Sergey Beryozkin < > > > >> > sberyozkin@gmail.com> napisa=B3: > > > >> > > > > >> > Hi > > > >> >> > > > >> >> 2010/7/29 =A3ukasz More=F1 > > > >> >> > > > >> >> > Hi, > > > >> >> > > > > >> >> > I'm still working on refactoring and changes in demo you > > suggested. > > > >> >> > I will likely update it tomorrow. > > > >> >> > > > > >> >> > I'll likely ask for some modifications but perhaps if you cou= ld > > > start > > > >> >> with > > > >> >> > > updating the demo > > > >> >> > > > > >> >> > such that a consumer initiates its own registration with the > > OAuth > > > >> >> server. > > > >> >> > > > > >> >> > > > > >> >> > I'm going to put high effort on my GSoC project next weeks. I > > would > > > >> >> really > > > >> >> > appreciate, > > > >> >> > if you would have some more modifications requests/directions > > which > > > >> >> project > > > >> >> > should go, as you have limited time next week > > > >> >> > and current changes will not take long. > > > >> >> > > > > >> >> > From what I'm seeing, I need to cover spec with code, simplif= y > > > >> >> > configuration > > > >> >> > and do more testing. > > > >> >> > > > > >> >> > > > > >> >> I have to sign off now...Please update the demo so that the > > consumer > > > >> >> registers itself, plus supplies a callback itself with a reques= t > > > token > > > >> >> request, add README and it would let users start experimenting. > > IMHO > > > >> the > > > >> >> initial phase can be considered complete once there's a demo > there > > > >> which > > > >> >> can > > > >> >> show users what they need to do. > > > >> >> > > > >> >> We can then discuss things further > > > >> >> > > > >> >> cheers, Sergey > > > >> >> > > > >> >> > > > >> >> > > > >> >> > Cheers, > > > >> >> > Lukasz > > > >> >> > > > > >> >> > 2010/7/29 Daniel Kulp > > > >> >> > > > > >> >> > > > > > >> >> > > You probably just need to change your deps to: > > > >> >> > > > > > >> >> > > geronimo-servlet_3.0_spec > > > >> >> > > > > > >> >> > > > > > >> >> > > Dan > > > >> >> > > > > > >> >> > > > > > >> >> > > On Thursday 29 July 2010 3:35:57 pm Sergey Beryozkin wrote: > > > >> >> > > > Hi Lucasz > > > >> >> > > > > > > >> >> > > > I can't build the oauth sandbox project, seeing > > > >> >> > > > [ERROR] FATAL ERROR > > > >> >> > > > [INFO] > > > >> >> > > > > > > >> >> > > > > >> > > -----------------------------------------------------------------------= - > > > >> >> > > > [INFO] Error building POM (may not be this project's POM)= . > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > Project ID: org.apache.cxf:cxf-rt-rs-oauth > > > >> >> > > > POM Location: > > > >> >> > > > > > > /home/sberyozkin/work/cxf/sandbox/oauth_1.0a/rt/rs/oauth/pom.xml > > > >> >> > > > Validation Messages: > > > >> >> > > > > > > >> >> > > > [0] 'dependencies.dependency.version' is missing for > > > >> >> > > > org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > Reason: Failed to validate POM for project > > > >> >> > org.apache.cxf:cxf-rt-rs-oauth > > > >> >> > > > at > > > >> /home/sberyozkin/work/cxf/sandbox/oauth_1.0a/rt/rs/oauth/pom.xml > > > >> >> > > > > > > >> >> > > > so I can not review the latest merge, sorry. I could've > tried > > > to > > > >> fix > > > >> >> > this > > > >> >> > > > issue but I'm not sure if you're finished with the > > refactoring > > > >> just > > > >> >> > yet. > > > >> >> > > > I'll be travelling tomorrow and I'll have some very limit= ed > > > time > > > >> >> during > > > >> >> > > the > > > >> >> > > > evenings next week but I'll try to provide some feedback = at > > > least > > > >> >> > > > > > > >> >> > > > cheers, Sergey > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > 2010/7/26 Sergey Beryozkin > > > >> >> > > > > > > >> >> > > > > Hi =A3ukasz > > > >> >> > > > > > > > >> >> > > > > 2010/7/26 =A3ukasz More=F1 > > > >> >> > > > > > > > >> >> > > > > Hi Sergey, > > > >> >> > > > > > > > >> >> > > > >> I'm really sorry for such commit, I know it shouldn't > > > happen. > > > >> I > > > >> >> > turned > > > >> >> > > > >> off checkstyle as i couldn't configure it properly on > > > intellij > > > >> >> and > > > >> >> > it > > > >> >> > > > >> was annoying during development. > > > >> >> > > > >> I will apply proper changes ASAP. > > > >> >> > > > >> > > > >> >> > > > >> no worries at all, I've broken the real builds with > > > checkstyle > > > >> >> > errors > > > >> >> > > so > > > >> >> > > > > > > > >> >> > > > > many times and it is the CXF sandbox after :-) > > > >> >> > > > > > > > >> >> > > > >> According to the demo, I built it as usual web-app, if > it > > > >> worked, > > > >> >> > use > > > >> >> > > > >> this same sources to deploy on GAE. > > > >> >> > > > >> However because of GAE restrictions it always needs > minor > > > >> changes > > > >> >> > > > >> before deploy, i.e. GAE can't read configuration files > > such > > > >> as: > > > >> >> > > > >> cxf-extension-http.xml > > > >> >> > > > >> from jars, so I copied it to WEB-INF folder. > > > >> >> > > > >> Commited to svn version does not depend on GAE SDK and > can > > > be > > > >> run > > > >> >> > > > >> locally with jetty:run. > > > >> >> > > > >> > > > >> >> > > > >> Yes, I warned about server configuration part:). I wil= l > > take > > > >> care > > > >> >> to > > > >> >> > > > >> make it simpler. > > > >> >> > > > > > > > >> >> > > > > I do not think it is too complicated - the simplificati= on > > can > > > >> be > > > >> >> done > > > >> >> > > > > once the whole flow is sound... > > > >> >> > > > > > > > >> >> > > > >> So far, oauth consumer properties are hardcoded and > > injected > > > >> into > > > >> >> > > > >> oauth provider, as I think it is not oauth library > > > >> responsibility > > > >> >> to > > > >> >> > > > >> deal with consumer registration. > > > >> >> > > > >> Hovewer for demo it would be good to have something li= ke > > > that. > > > >> I > > > >> >> > would > > > >> >> > > > >> do registration form at the server as it is done by > > current > > > >> big > > > >> >> > oauth > > > >> >> > > > >> implementations. > > > >> >> > > > > > > > >> >> > > > > I agree that conceptually the registration of consumers > is > > a > > > >> >> separate > > > >> >> > > > > issue. But it is part of the solution that users will b= e > > > >> >> eventually > > > >> >> > > > > offering so just showing them that the consumers have t= o > go > > > and > > > >> >> > > register > > > >> >> > > > > themselves with help people with coming up with some > custom > > > >> >> > > registration > > > >> >> > > > > forms, etc. The registration does not have to be done a= t > > the > > > >> >> server > > > >> >> > > > > hosting the resource, it is just important for the OAut= h > > > >> provider > > > >> >> be > > > >> >> > > > > able to get to the consumer details. I'm fine with > assuming > > > at > > > >> the > > > >> >> > > > > moment that the registration handler is collocated with > the > > > >> >> > > > > endpoints/providers enforcing OAuth flow. > > > >> >> > > > > > > > >> >> > > > > But the callback uri which is being injected at the > moment > > > >> should > > > >> >> go > > > >> >> > > > > anyway given that it is part of the actual flow, > > > specifically, > > > >> the > > > >> >> > > > > consumer provides it during the request token request > > > >> >> > > > > > > > >> >> > > > >> Recently I've noticed that Camel have done oauth clien= t > as > > > >> >> well:): > > > >> >> > > > >> http://camel.apache.org/tutorial-oauth.html > > > >> >> > > > >> > > > >> >> > > > >> Thanks much for review, and hints. > > > >> >> > > > > > > > >> >> > > > > thanks for your effort :-) > > > >> >> > > > > > > > >> >> > > > > Sergey > > > >> >> > > > > > > > >> >> > > > >> Cheers, > > > >> >> > > > >> Lukasz > > > >> >> > > > >> > > > >> >> > > > >> 2010/7/24 Sergey Beryozkin : > > > >> >> > > > >> > Hi =A3ukasz > > > >> >> > > > >> > > > > >> >> > > > >> > Sorry for a delay, I should've come back earlier to > > you. > > > >> >> > > > >> > > > > >> >> > > > >> > I've run the demo hosted at the app engine and I thi= nk > > > from > > > >> the > > > >> >> > > > >> > > > >> >> > > > >> education > > > >> >> > > > >> > > > >> >> > > > >> > point of view it is a good demo and it is handy one > does > > > not > > > >> >> even > > > >> >> > > has > > > >> >> > > > >> > to build anything in order to try it. > > > >> >> > > > >> > > > > >> >> > > > >> > I've had a problem building the rt/rs/oauth tests - > > > there's > > > >> a > > > >> >> > bunch > > > >> >> > > of > > > >> >> > > > >> > CheckStyle errors. Can you please build > > sandbox/oauth_1.0a > > > >> from > > > >> >> > the > > > >> >> > > > >> > > > >> >> > > > >> trunk, > > > >> >> > > > >> > > > >> >> > > > >> > just do 'mvn install -Pfastinstall' and then do 'mvn > > > >> install' > > > >> >> from > > > >> >> > > > >> > > > >> >> > > > >> rt/rs/ ? > > > >> >> > > > >> > > > >> >> > > > >> > One other thing, please move the demo to > > > >> >> > > > >> > "distribution/src/main/release/samples/" as well add > > > Readme > > > >> to > > > >> >> it. > > > >> >> > > > >> > > > > >> >> > > > >> > Also I can not build the demo too, the client build > > fails > > > >> with > > > >> >> the > > > >> >> > > > >> > > > >> >> > > > >> following > > > >> >> > > > >> > > > >> >> > > > >> > dependency missing > > > >> >> > > > >> > 1) net.oauth.core:oauth-consumer:jar:20100527 > > > >> >> > > > >> > > > > >> >> > > > >> > But I'm seeing an oauth repo in the rt/rs/oauth pom, > > have > > > >> you > > > >> >> > built > > > >> >> > > it > > > >> >> > > > >> > > > >> >> > > > >> in > > > >> >> > > > >> > > > >> >> > > > >> > the GAE dev environment ? > > > >> >> > > > >> > > > > >> >> > > > >> > Can you please spend a bit of time on cleaning the > build > > a > > > >> bit > > > >> >> : > > > >> >> > > > >> > - fix the checkstyle errors and move the demo to the > > > >> >> > > > >> > ""distribution/src/main/release/samples/"" area and > also > > > add > > > >> >> > Readme; > > > >> >> > > > >> > > > >> >> > > > >> after > > > >> >> > > > >> > > > >> >> > > > >> > building the distribution (mvn install in > > > >> trunk/distribution) > > > >> >> you > > > >> >> > > can > > > >> >> > > > >> > > > >> >> > > > >> easily > > > >> >> > > > >> > > > >> >> > > > >> > verify the demo can be run by locating in the target= . > > > >> >> > > > >> > - add the oauth dependency in the parent pom so that > the > > > >> >> rs/oauth > > > >> >> > > > >> > module > > > >> >> > > > >> > > > >> >> > > > >> can > > > >> >> > > > >> > > > >> >> > > > >> > depend on it without specifying a version and have t= he > > > demo > > > >> >> client > > > >> >> > > > >> > > > >> >> > > > >> module > > > >> >> > > > >> > > > >> >> > > > >> > depending on rt/rs/oauth module instead (similarly t= o > > the > > > >> >> server > > > >> >> > > one) > > > >> >> > > > >> > - during the main build please use the Spring versio= n > > CXF > > > >> >> depends > > > >> >> > > upon > > > >> >> > > > >> > > > >> >> > > > >> and > > > >> >> > > > >> > > > >> >> > > > >> > use its -Pspring3 profile to build for the deploymen= t > > into > > > >> GAE > > > >> >> > > > >> > > > > >> >> > > > >> > As far as the demo is concerned. I looked at the > server > > > part > > > >> >> and > > > >> >> > it > > > >> >> > > > >> > > > >> >> > > > >> looks > > > >> >> > > > >> > > > >> >> > > > >> > complicated enough :-) but I think it makes sense to > me. > > > >> I'll > > > >> >> > likely > > > >> >> > > > >> > ask > > > >> >> > > > >> > > > >> >> > > > >> for > > > >> >> > > > >> > > > >> >> > > > >> > some modifications but perhaps if you could start wi= th > > > >> updating > > > >> >> > the > > > >> >> > > > >> > demo such that a consumer initiates its own > registration > > > >> with > > > >> >> the > > > >> >> > > > >> > OAuth > > > >> >> > > > >> > > > >> >> > > > >> server : > > > >> >> > > > >> > I can see at the moment an oauth provider is injecte= d > > with > > > >> some > > > >> >> > > sample > > > >> >> > > > >> > consumer properties. I'm not sure what is the best w= ay > > to > > > do > > > >> it > > > >> >> : > > > >> >> > > may > > > >> >> > > > >> > be > > > >> >> > > > >> > > > >> >> > > > >> the > > > >> >> > > > >> > > > >> >> > > > >> > server can return a registration form or the client > can > > > just > > > >> >> push > > > >> >> > > the > > > >> >> > > > >> > registration info itself. > > > >> >> > > > >> > > > > >> >> > > > >> > Overall I think it is a good progress indeed > especially > > > >> given > > > >> >> the > > > >> >> > > > >> > > > >> >> > > > >> complexity > > > >> >> > > > >> > > > >> >> > > > >> > of the whole effort. > > > >> >> > > > >> > > > > >> >> > > > >> > > > > >> >> > > > >> > > > > >> >> > > > >> > thanks, Sergey > > > >> >> > > > >> > > > > >> >> > > > >> > On Wed, Jul 14, 2010 at 10:14 PM, =A3ukasz More=F1 < > > > >> >> > > lukasz.moren@gmail.com > > > >> >> > > > >> > > > > >> >> > > > >> >wrote: > > > >> >> > > > >> >> Hi all, > > > >> >> > > > >> >> > > > >> >> > > > >> >> I have managed to create two sample OAuth > aplications: > > > >> >> > > > >> >> ordinary OAuth 1.0a client: > > > >> >> http://www.oauthclient.appspot.com > > > >> >> > > > >> >> and authorization server that uses CXF OAuth module= : > > > >> >> > > > >> >> http://www.cxfoauthserver.appspot.com > > > >> >> > > > >> >> > > > >> >> > > > >> >> Both sample applications and changes in oauth libra= ry > > are > > > >> >> > commited > > > >> >> > > in > > > >> >> > > > >> >> sandbox. > > > >> >> > > > >> >> > > > >> >> > > > >> >> OAuth configuration in sample authorization server > app > > > >> looks a > > > >> >> > bit > > > >> >> > > > >> >> awfully but I think most of that can be hidden and > done > > > out > > > >> of > > > >> >> > > band. > > > >> >> > > > >> >> There is still some areas in specification not > covered > > by > > > >> >> > > > >> >> implementation, so I would like to take care of tha= t > in > > > >> next > > > >> >> > steps. > > > >> >> > > > >> >> > > > >> >> > > > >> >> Thanks in advance for some feedback. > > > >> >> > > > >> >> > > > >> >> > > > >> >> Cheers, > > > >> >> > > > >> >> Lukasz > > > >> >> > > > > > >> >> > > -- > > > >> >> > > Daniel Kulp > > > >> >> > > dkulp@apache.org > > > >> >> > > http://dankulp.com/blog > > > >> >> > > > > > >> >> > > > > >> >> > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > --000e0cd1f8c880ac5d048dc77385--