openWallet is a single sign-on (SSO) solution for the internet. It differs from other SSO solutions (such as MS Passport) in that the user is in charge of their own data, rather that some centralized or third party repository.
Be the first to post a text review of openWallet. Rate and review a project by clicking thumbs up or thumbs down in the right column.
* 0.0.1 * Fixed defect in retrieving from the database. * 0.0.0 * Initial Release
True single sign-on for the internet is now a possibility with the first release of openWallet. The code is in a very alpha stage, but key functionality is implemented and working, completeing the intial PoC phase. Users test the system at http://www.howardfamily.id.au/openwallet.php where they can login using the openWallet client, their OpenPGP key and passphrase.
The openWallet project has chose to use Jetty (http://jetty.mortbay.org/jetty/) to implement the openWallet client. Jetty is a light weight 100% java HTTP server, which is easily embeddable in application, making it an ideal candidate for this project.
Well, after a couple of years of this project just sitting idle, I've finally created a proof of concept on the project homepage. In the PoC, a timestamp is sent to the client, which signs it and sends it back to the website for verification. Currently the website doesn't validate the signature, but that's the easy bit. The hard bit was finding a nice simple way for the website to communicate with the client on the users machine. How is this done in the end? It's so simple that I can't belive I didn't think of it earlier. The site redirects to a localhost URL and the browser does the rest. Simple and clean. Love it.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: