social.colibri.beta.community.registerCredentials

Hands the AppView credentials for a community hosted elsewhere, so it can administer a community it did not create. The password is stored encrypted at rest.

Repository @colibri.social did:plc:mprdjqjluoswa7awzggaggj3 namespace authority
Details · procedure
Kindprocedure
Authoritycommunity.beta.colibri.social
Indexed

Procedure

procedure · POST

Input

application/json

community

requiredstring · did

The community the credentials belong to.

identifier

requiredstring

The identifier used to authenticate with the community's PDS, such as its handle or DID.

password

requiredstring

The password or app password used to authenticate with the community's PDS.

Output

application/json

Errors

AuthRequired

The request is missing, malformed, or unverifiable service auth.

Forbidden

The requesting user lacks permission to register credentials for this community.

InvalidRequest

The arguments are inconsistent or malformed beyond schema validation.

CredentialsRejected

The PDS refused the identifier and password.

UpstreamFailure

A PDS or third-party call the AppView depends on failed.

Similar lexicons

semantic match

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

  • social.colibri.community.registerCredentials

    procedure not from the namespace authority

    Registers bring-your-own PDS credentials for a community DID.

  • Adopts an existing account as a community: this AppView takes custody of its credentials, creates the four community spaces on whichever PDS already hosts it, and seeds the same starter layout social.colibri.beta.community.create does. The account keeps its own DID, handle and PDS, and the caller becomes its owner. Use this instead of community.create to bring your own DID.

  • social.colibri.community.create

    procedure not from the namespace authority

    Creates a community, bootstrapping its DID repo with a default category, channel, owner role, and member record.

  • Starts a sign-in as a community host account. The requesting user opens the returned URL, signs in as that account on its own server and allows the AppView to act for it. The AppView then adopts the account as a new community, or reconnects an existing community after its sign-in lapsed or its account moved. Poll getHostAuthorization with the returned request to learn the outcome.

  • Admits the requesting user to a community. Joining is an AppView procedure rather than a record the user writes, because admission is what makes the community's spaces readable to them.