Skip to content

Passwords: change, admin reset, forced-reset lock

Only a self-service password change clears the forced-reset flag; an admin's reset leaves it set and ends the account's other sessions, not the one making it.

A password can change two ways — a user proving their own current one, or a site admin setting a new one directly — and both land on the same one route; a profile save can't touch a password at all. Which way it happened is what decides what else moves: the forced-reset flag, the account's other sessions, and whether the person making the change stays signed in.

Proving it yourself, or having it set for you

Changing your own password has to prove the current one first, checked against the same brute-force lockout that guards login. A site admin setting someone else's password skips that proof, but the trade is a harder rank check than most admin actions: outranking the target, not just matching them. A site admin can reset an author's or an editor's password — never a fellow site admin's.

What a password change ends, and what it leaves running

Either kind of change invalidates every refresh token issued before it, so every other device or browser signed in under the old password loses the ability to renew its session. It does not revoke access tokens already handed out — those keep working until they expire on their own, up to fifteen minutes later. A self-service change hands back a fresh token pair in the same response, so the person making it stays signed in; an admin-set reset doesn't do that, because it was never the admin's own session to begin with.

API keys sit outside all of this. A key authenticates as its owner, but there's no one at the other end to satisfy a reset, so a forced-reset flag on a user's account never blocks the requests their keys are making. Freezing automation is a different action — deactivate the user or revoke the key.