space.highport.manage.grantSpaceAccess

Give bard a delegation token so it can keep reading a space. Any member can call this with a token they issued. Bard trades it for a credential, renews its notification registration when due, and catches up on anything it missed.

Details · procedure
Kindprocedure
Authoritymanage.highport.space
Indexed

Procedure

procedure · POST

Input

application/json

delegationToken

requiredstring

A delegation token the caller minted for this space. Used once and never stored.

space

requiredstring · at-uri

Output

application/json

accessExpiresAt

requiredstring · datetime

When bard's new credential expires.

drained

requiredinteger

Queued notifications this grant turned into sync jobs.

registrationExpiresAt

string · datetime

When bard's notification registration with the space host expires.

Errors

SpaceNotFound

Bard is not connected to that space. Call connectSpace first.

GrantIssuerMismatch

The delegation token was not issued by the caller.

GrantExpired

The delegation token has expired.

GrantRefused

The space host refused the exchange.

AppNotAllowed

The space does not allow bard access.

SpacesDisabled

Space support is disabled on this deployment.

Similar lexicons

semantic match

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

  • Connect a space so bard can read and publish the authority's site and tile records from it. Only the authority can call this, with a delegation token it issued. Bard trades the token for a credential, registers for notifications, and pulls the authority's repo. Safe to repeat.

  • Hands the AppView access to one of the requesting user's personal spaces. The client mints a delegation token on its own PDS for the space and passes it here, because a delegation token is single-use and short-lived and the AppView has no OAuth session of its own. The AppView exchanges the token for a space credential and syncs the space.

  • Issue a space credential (JWT) for a space the caller is a member of. The credential is multi-use until it expires and is bound to the caller's DPoP key (cnf.jkt, RFC 9449): it must be presented under the DPoP auth scheme with a per-request proof signed by that key. It is signed by the space authority's signing key so any repo host can verify it without contacting the authority. Identity is resolved from a delegation token when provided (a standalone DPoP proof in the DPoP header supplies the ke

  • What bard knows about a connected space: its sync state, when bard's credential expires, and its counts. Available to the space's authority and to viewers (identities with a grant inside the viewer window).