Chelabase
ManagementMembers

List a member's personal logins

GET
/v1/members/{member_id}/personal-logins

Any status. Filtered by the caller: a member sees all of their own, a tenant admin all of anyone's, an Admin of a project the logins on that project's databases; anyone else gets an empty list. Never a password or verifier.

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

member_id*string

Member id

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/personal-logins"
{  "logins": [    {      "created_at": "2019-08-24T14:15:22Z",      "database_id": "91088904-0b92-46ad-9240-e1afa0da22df",      "database_name": "string",      "member_id": "435a4844-006a-4cfc-a644-e8eb2dd2ca43",      "project_id": "405d8375-3514-403b-8c43-83ae74cfe0e9",      "revoked_at": "2019-08-24T14:15:22Z",      "revoked_reason": "access_lost",      "role_name": "string",      "status": "active",      "valid_until": "2019-08-24T14:15:22Z"    }  ]}

Decline a sign-up POST

The pending member becomes `removed` (one `member_declined` event), then, as for a removal, their personal logins are revoked, their account's sessions end when they are an active member of no other tenant, and the account is banned when no other tenant holds them at all. A still-valid token is refused at once. Every step runs even when one fails; declining a removed member again redoes those steps.

Reinstate a suspended member POST

The member is active again with their grants; a ban Chelabase placed on their account when they were removed is lifted, and their offboarded mark is cleared. An account banned for any other reason is 409 `conflict` and nothing changes: the member stays suspended until that ban is lifted. Their personal logins stay revoked: they make new ones. Reinstating an active member again redoes the account steps.