Skip to content
This repository has been archived by the owner on May 8, 2018. It is now read-only.

Grendel sessions #4

Open
precipice opened this issue Jan 6, 2010 · 5 comments
Open

Grendel sessions #4

precipice opened this issue Jan 6, 2010 · 5 comments

Comments

@precipice
Copy link
Member

It would be good to be able to have a session handle that would allow access to Grendel without having to store the plaintext password during the session. For instance, let me create a session on user login, use that session during the user's session on the site, and destroy it when they log out.

@codahale
Copy link
Contributor

codahale commented Jan 7, 2010

Sam and I talked about this — we'd need to cache the UnlockedKeySet of the user in memory.

@stephanwehner
Copy link

I thought the way to handle this is to would store a key in the cookie, and the UnlockedKeySet, encrypted with that key on the server. Link the two with a database id (since more than one user will be logged in)

Something wrong with that ?

Stephan

@codahale
Copy link
Contributor

Stephan — that's not at all different from how Grendel uses KeySet and the user's password.

@stephanwehner
Copy link

Then I guess I don't quite understand the original question.

Isn't the "key in the cookie" I mentioned going to be the "session handle" that precipice is asking about?

Stephan

@codahale
Copy link
Contributor

No. It would be a random session ID. We already have this designed; this ticket is just a reminder for us to actually implement it.

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

No branches or pull requests

3 participants