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.


http://windyroad.org/openwallet





Separate each tag with a space.

Release Date:

2007-09-17

Topic:

Operating System:

License:

Translations:

Intended Audience:

User Interface:

Programming Language:

Registered:

2004-07-02

Ratings and Reviews

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.

Project Feed

  • openWallet for WordPress 0.0.1 file released: openwallet-0.0.1.zip

    * 0.0.1 * Fixed defect in retrieving from the database. * 0.0.0 * Initial Release

    posted 800 days ago

  • File released: /openWallet-client/0.0.0/openWallet-Client-0.0.0.zip

    posted 800 days ago

  • openWallet-client 0.0.0 file released: openWallet-Client-0.0.0.zip

    posted 800 days ago

  • File released: /openWallet for WordPress/0.0.1/openwallet-0.0.1.zip

    posted 800 days ago

  • openWallet 0.1 Released

    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.

    posted by tomhoward 1351 days ago

  • openWallet chooses Jetty

    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.

    posted by tomhoward 1376 days ago

  • Proof of Concept

    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.

    posted by tomhoward 1376 days ago

  • Code committed

    Anonymous committed patchset 1 of module CVSROOT to the openWallet CVS repository, changing 11 files

    posted by nobody 1972 days ago

  • Forum thread added

    Anonymous created the Welcome to Developers forum thread

    posted by nobody 1972 days ago

  • Forum thread added

    Anonymous created the Welcome to Help forum thread

    posted by nobody 1972 days ago

Rate and Review

Be the first person to add a text review.

Would you recommend this project?






<

Related Projects

openWallet Actions

Thanks for your rating!

Would you also like to write a review?





Skip Review

Thanks for your review!

Get credit for your review by logging in via OpenID. Click your account provider:

No Thanks