at.blueharbor.createSession

The lxm named in service-auth JWTs minted for the BlueHarbor backend (aud did:web:blueharbor.at). The backend verifies the JWT against the caller's DID document and exchanges it for a BlueHarbor session token. Defined here so the method identifier resolves; the HTTP call itself is served by the BlueHarbor service, not a PDS.

Repository @toddlambert.com did:plc:r5pj64joaywqnvk2obembpt7 namespace authority
Details · procedure
Kindprocedure
Authorityblueharbor.at
Indexed

Procedure

procedure · POST

Output

application/json

did

requiredstring · did

expiresAt

requiredinteger

token

requiredstring

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Exchange a PDS-minted service auth token for a gateway session. The service auth JWT travels in the Authorization header (aud = the gateway DID, lxm = this NSID) and is single-use. Browser callers (Origin header present) receive the session as an HttpOnly cookie and no sessionToken is returned.

  • Get a signed token on behalf of the requesting DID for the requested service.

  • social.dept.createSession

    procedure not from the namespace authority

    Start a Social Dept. session for the account that signed the service auth token sent as the bearer credential. The token's lxm must be this method.

  • Exchange a proxied service-auth call for a short-lived direct-access token bound to the viewer's DID.

  • Mint a service-auth JWT whose issuer is this repo's DID, signed by the knot that owns the repo's signing key. When calling this, you'll need the same perms as git push, ie. being repo owner/collaborator/knot-admin.