{ "attachments": [], "comments_archived": true, "date": "2006-04-06T13:46:38.000Z", "layout": "post", "tags": [ "asides" ], "title": "Private client-side cookies for AJAX?", "wordpress_id": 925, "wordpress_slug": "private-client-side-cookies-for-ajax", "wordpress_url": "http://decafbad.com/blog/2006/04/06/private-client-side-cookies-for-ajax", "year": "2006", "month": "04", "day": "06", "isDir": false, "slug": "private-client-side-cookies-for-ajax", "type": "entry", "postName": "2006-04-06-private-client-side-cookies-for-ajax", "html": "

Along with the S3 stuff I'm poking at in AJAX, I'd like to retain the user's key ID and secret for S3 locally so that it doesn't need to be reentered all the time or stuck into constants on a server-held file. But, I don't want to stick it into cookies or anything that will go over the wire - since the whole point of the HMAC authentication is to prevent that from happening.

\n

I've looked at AMASS, but it appears to be broken on Mac - which is a non-starter for me on my PowerBook. I'm wondering if there's any other practical way to retain a pair of strings locally across browsers for an AJAX app. Because, beyond just that bit of local storage requirement, I've got entire vistas of persistence available on S3.

\n

I suppose I could stick the credentials in a cookie, then further encrypt them with a friendlier username / passphrase. The main issue I see with constantly reentering the credentials is that they're these big honking strings that I'll never be able to remember like a username and password.

\n\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "

Along with the S3 stuff I'm poking at in AJAX, I'd like to retain the user's key ID and secret for S3 locally so that it doesn't need to be reentered all the time or stuck into constants on a server-held file. But, I don't want to stick it into cookies or anything that will go over the wire - since the whole point of the HMAC authentication is to prevent that from happening.

\r\n

I've looked at AMASS, but it appears to be broken on Mac - which is a non-starter for me on my PowerBook. I'm wondering if there's any other practical way to retain a pair of strings locally across browsers for an AJAX app. Because, beyond just that bit of local storage requirement, I've got entire vistas of persistence available on S3.

\r\n

I suppose I could stick the credentials in a cookie, then further encrypt them with a friendlier username / passphrase. The main issue I see with constantly reentering the credentials is that they're these big honking strings that I'll never be able to remember like a username and password.

\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2006", "path": "2006/04/06/private-client-side-cookies-for-ajax", "needsBuild": true, "prevPostPath": "2006/04/06/upload-from-local-file-via-ajax", "prevPostTitle": "Upload from local file via AJAX?", "nextPostPath": "2006/04/06/parameterize-your-service-url-for-the-s3-rest-api", "nextPostTitle": "Parameterize your service URL for the S3 REST API" }