Lexicon Garden

org.tangled.repo.mintToken

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.

Repository @tangled.org did:plc:wshs7t2adsemcrrd4snkeqli namespace authority
Details · procedure
Kindprocedure
Authorityrepo.tangled.org
Indexed

Showing version bafyreicnlsfce7h3qndo6ayvul2ft3rpozh56tdgvzf5ordcecj3phfrc4. Show the latest

Compare Edit in builder → Fork →

Procedure

procedure · POST

Input

application/json

aud

requiredstring · did

Audience of the minted token, a DID service ref for the service, that the token is addressed to.

exp

requiredinteger

Unix seconds. Must be in the future, and at most 60s after mint time.

lxm

requiredstring · nsid

Lexicon method to which minted token binds.

repo

requiredstring · did

DID of the repo that becomes the token's issuer. Must be the audience of a given calling session.

Output

application/json

token

requiredstring

The signed service-auth JWT.

Similar lexicons

semantic match

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

  • com.atproto.server.getServiceAuth

    query

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

  • at.blueharbor.createSession

    procedure

    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.

  • org.tangled.repo.reserveKey

    procedure

    Reserve a repo identity under a DID the caller brings. The knot seals and holds a signing key for the repo DID; the caller publishes the matching public key in that DID's document before calling org.tangled.repo.createRepo with the same DID.