Reference
Arcane.users.verifyShell()
Verifies the user's Arcane shell configuration.
This focused page is derived from the mechanically checked full member inventory.
Syntax
Arcane.users.verifyShell(username)
Parameters
Username
Return value
Promise<{user, operation, credentials}>
Description
Verifies the user's Arcane shell configuration.
Overview
Arcane.users.verifyShell(username) performs an administrator-backed,
read-only verification of the recorded account's exact Arcane shell binding.
It requires users.manage, the Provisioner type, and privileged Core access,
but it does not change the shell. Microsoft NT verifies both protected per-user
bindings; Linux verifies the protected login-shell field.
Result and events
The exact result is {user, operation, credentials} with empty credentials.
user is the current host-specific users.list() record plus
administratorVerified: true and an administratorVerifiedAt timestamp.
Inspect user.shellAssigned; administrative verification can successfully
complete while reporting a mismatch. Standard operation events are emitted.
Errors and recovery
NOT_ARCANE_USER means no managed recovery record exists. USER_NOT_FOUND
means the recorded account is gone. Profile, registry, passwd, SID, or uid
verification errors require administrator review. Do not call
restoreShell() merely because verification failed to run; restore only after
reviewing a valid mismatch and the recorded baseline.
Example
const verification = await Arcane.users.verifyShell('arcane-user');
if (!verification.user.shellAssigned) {
console.warn('The recorded Arcane shell binding does not match.');
}