The library documents itself · Security & governance
stzAuthResponder
8 own methods · 0 forms written with extensions, listed under their method
the source: base/security/stzResponsePlan.ring(opens in a new tab) · All classes · The area reference: Security & governance
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
init
(no comment in the source: the name reads as a sentence) initno extension
Owns
(no comment in the source: the name reads as a sentence) ownsno extension
LockAccount
The account is closed: every login path and every live session refuse.no extension
RevokeSession
The plan targets an ACTOR, so every session of that user ends.no extension
RotateSecret
Not this responder's to perform: authentication owns accounts and sessions, nothing else. A plan that proposes these needs another responder -- refused loudly, never pretended.no extension
RevokeCapability
(no comment in the source: the name reads as a sentence) revoke capabilityno extension
ShedSource
(no comment in the source: the name reads as a sentence) shed sourceno extension
QuarantinePart
(no comment in the source: the name reads as a sentence) quarantine partno extension