keyapi about sdc-cloudapi HOT 3 CLOSED

Sorry for the delay.

Okay, here's the deal: if you want to make cloudapi calls using token authentication, you need to provide http-signature details signed using the caller's account (e.g. you need an account for your portal, since the portal is on the other side of the HTTP request). The X-Auth-Token stuffed with the keyapi token contains the details about the user the portal is calling on behalf of.

Basically, your headers would look something like the following:

Authorization: Signature keyId="/<your portal or ops account>/keys/<some portal key>",algorithm="RSA-SHA256" <base64-encoded http-signature chunk>
X-Auth-Token: {"keyid":"<keyapi-generated UUID","data":"<base64 data about the portal's user initiating this call>","version":"0.1.0","hash":"<base64 hash of data>"}

Authorization is the http-signature for your portal. X-Auth-Token is the token provided by keyapi on behalf of the user using your portal.

I hope that clarifies things. My apologies that there are no docs about it. I'll at least improve the big-theory statement at the top of cloudapi's auth.js.

from sdc-cloudapi.

@arekinath this issue has been sitting open for a while. Do we have an open JIRA ticket associated with it, or an RFD or mailing list discussion? Or is it safe to close this GitHub issue?

from sdc-cloudapi.

Safe to close. The keyapi repo was opened up.

from sdc-cloudapi.