Hi, Yes photark should be lightweight. Dependencies are scary things and we should avoid using heavy libs which has lot of dependencies.dyuproject seems to good and lightweight lib.Online demo[1] also available.
[1]http://dyuproject.appspot.com/ On Sat, Mar 27, 2010 at 10:29 PM, Suhothayan Sriskandarajah < [email protected]> wrote: > On 25 March 2010 10:14, Suhothayan Sriskandarajah <[email protected] > >wrote: > > > first of all i apologise for giving wrong information saying that jOpenID > > only supporting Google. > > It does support other OpenID providers. > > but it doesn't have discovery and we have to manually add the supported > > open id providers. > > this is what i found at the FAQ on jOpenID[1] > > > > "I saw some web sites allow users enter their emails or URLs to find the > >> OP's sign on page > >> > >> Yes OpenID standards contains two parts: discovery and authentication. > >> Discovery is the process where the RP uses email or URL to look up the > >> address of OP. It is complex, and may confuse the end users. > >> > >> Instead, Web UI designer should give end users the chooses of their > >> familiar OpenID accounts, such as Google account, Yahoo account, etc. > >> > >> JOpenID only supports OpenID authentication because the discovery > protocol > >> is hard to use, and difficult to implement. You will find that JOpenID > meets > >> your 99.9% requirements. > >> > >> How can I add more OpenID Providers > >> > >> As we discussed before, JOpenID does not support discovery, which means > >> you should provide a list of OPs to end users. All OPs are list in > >> openid-providers.properties file. If you want to add more OPs, try to > find > >> their URL with a little effort. If you think JOpenID should contain more > >> popular OPs, please add a comment with the OP's URL." > >> > > > > and for the maven repository > > jopenID doesn't have one, but i have found a user has add one before. > check > > the link[2] > > > > [1]http://code.google.com/p/jopenid/wiki/FAQ > > [2]http://code.google.com/p/jopenid/issues/detail?id=2&can=1&q=maven > > > > dyuproject has maven repo; > > http://dyuproject.googlecode.com/svn/repos/maven2/ > > > > joid has maven repo; > > http://mirrors.kokila.it/maven2/joid/ > > > > openid4java maven repo; > > http://ftp.us.xemacs.org/pub/mirrors/maven2/org/openid4java/ > > > > > i thought of selecting dyuproject to implement this project, > this is because... > 1. jopenID cant be used since it doesn't have a maven repo. > 2. its the 2nd most smallest library next to jopenID > 3. it have proper documentation > 4. some other Apache projects also have used this. eg. sling > https://issues.apache.org/jira/browse/SLING-839 > [but roler, jetspeed have used openid4java] > > And most importantly as our main goal is producing a light weight product. > > therefore i thought of going with this. > please give your suggestions. > > regards, > Suho > > > regards > > Suho > > > > > > > > On 23 March 2010 21:06, Suhothayan Sriskandarajah <[email protected]> > > wrote: > > > On 23 March 2010 10:24, Avdhesh Yadav <[email protected]> wrote: > > >> Hi, > > >> > > >> I think a simple library which supports Relying Party is enough for > this > > >> project. > > >> > > >> I find some more simple open id libraries and they are apache v2. > > >> I think you should first evaluate these libs. > > >> > > >> http://code.google.com/p/jopenid/ > > >> http://code.google.com/p/dyuproject/ > > >> http://code.google.com/p/joid/ > > >> > > >> Thoughts ? > > >> > > > > > > i found several libraries in [1] and when i'm going throught them > > > i found these... > > > > > > openid4java > > > + has many feathers > > > - poor documentation but the wiki and examples are helpful > > > - have to do a bit of coding in order to implement > > > http://www.ibm.com/developerworks/java/library/j-openid/index.html > > > > > > wso2 identity server > > > +build on top of openid4Java so it has all the openid4Java's fetchers > > > +no much coding and can be implemented vary easily > > > http://wso2.org/projects/identity > > > > > > jopenid > > > seems ok > > > -only Google Federated Login is allowed > > > > > > dyuproject > > > java REST framework servlet-based,json alternative > > > supports OAuth (we may need in futuer) > > > http://www.ohloh.net/p/dyuproject > > > <i couldn't get much info about it> > > > > > > joid > > > +simple api > > > -can be uses in simple cases (like PhotArk's) not sure whether it will > > > be a bottle neck in future > > > <i couldn't get much info about it> > > > > > > > > > [1]http://openid.net/developers/libraries/ > > > > > > > > > these are some i found today i'll update you as soon as i get more > > > info. since we are only intersected in building the relying party and > > > as our task have only primitive things all these seems ok > > > > > > please give your preferences > > > > > > Regards > > > Suho > > > > > >> -- > > >> Avdhesh Yadav > > >> http://www.avdheshyadav.com > > >> > > >> > > >> On Mon, Mar 22, 2010 at 10:56 PM, Suhothayan Sriskandarajah < > > >> [email protected]> wrote: > > >> > > >>> hi, > > >>> > > >>> i thought of using OpenID4Java library[1] for the project "Integrate > > >>> OpenID with PhotArk". > > >>> > > >>> This library allows us to enable OpenID for Java webapps > > >>> > > >>> it is licensed under Apache v2 > > >>> it has Identity Provider and it is openID 2.0 Compatible > > >>> > > >>> i believe this would be fine for PhotArk. > > >>> > > >>> if you have any other suggestions please let me know. > > >>> > > >>> [1]http://code.google.com/p/openid4java/ > > >>> > > >>> Regards > > >>> Suho > > >>> > > >> > > > > > > > > -- Avdhesh Yadav http://www.avdheshyadav.com
