Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StatelessServerAssociationStore #193

Open
GoogleCodeExporter opened this issue Jun 4, 2015 · 1 comment
Open

StatelessServerAssociationStore #193

GoogleCodeExporter opened this issue Jun 4, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Right now OpenID4Java comes with two implementations for 
ServerAssociationStore, being the InMemoryServerAssociationStore and the 
JdbcServerAssociationStore. While these implementations work just fine for most 
deployments, they could pose some problems when there is a need for high 
scalability where you run multiple instances of your OP and you don't want the 
database to become a bottleneck.

For such deployments, a stateless implementation of the ServerAssociationStore 
could be interesting. Here all instances of ServerAssociationStore share an AES 
secret key. This secret key is used to encode all information of the 
association within the association handle itself. This way, multiple 
independent OP instances can work with the same associations, even without 
explicitly communicating them with each other (via database or some messaging 
system).

I've implemented such a StatelessServerAssociationStore as part of the eID IdP 
project. See also: http://code.google.com/p/eid-idp/source/detail?r=455

It would be interested if OpenID4Java provided a reference implementation of 
this mechanism.


Original issue reported on code.google.com by [email protected] on 25 Feb 2013 at 1:14

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant