Expand description
bot.did.updateCredentials: what logs in as an account, changed after
it is created.
Two callers. The account replaces the key that signed the request with
one new key, which signs addProof. The operator adds a credential,
removes one, or both, on any account but the server’s own. Either way
the change is one commit, made by Registry::update_credentials.
Structs§
- Change
Request 🔒 - The change a body asks for. The dashboard’s route names the account in its path, so its body is this alone.
- Owned
Change 🔒 - A
CredentialChangethat can cross into a blocking task. - Update
Credentials 🔒Request - Body of
bot.did.updateCredentials.
Constants§
- METHOD 🔒
- The method, as a key proof’s
lxmnames it.
Functions§
- add_
proof_ 🔒invalid - change_
credentials 🔒 - The change
requestasks ofdid, by the operator whenby_operator. - check_
add_ 🔒proof addProof: a JWT the added key signed as the account, for this server and this method, spent here.- parse_
add 🔒 - The request’s
add,parkedKeyandremove, checked for shape. - prove_
account 🔒 - The account’s own JWT: a key proof whose
issisdid, for this server and this method, spent here. Answers the key that signed it. - require_
replace 🔒 - Refuses an account’s change that is not one key replacing the key that signed the request.
- take_
parked 🔒 - The key parked under the account’s hostname with
fingerprint, taken, for the account’s kind. - update_
credentials 🔒 POST /xrpc/bot.did.updateCredentials- update_
credentials_ 🔒from_ dashboard POST /dashboard/api/accounts/{did}/credentials: the operator’s change, at a path the dashboard’s session cookie reaches. That cookie is scoped to/dashboard, so a browser never carries it to/xrpc.- update_
credentials_ 🔒inner