{"version":"2.1.225","anchor":"trusted-device-403s-handled-on-elevated-auth-requests","canonical_anchor":"trusted-device-403s-handled-on-elevated-auth-requests","heading":"Trusted-device 403s handled on elevated-auth requests","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/trusted-device-403s-handled-on-elevated-auth-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Trusted-device 403s handled on elevated-auth requests\n\nA rejected session can now tell you it's stale and needs re-login, not just untrusted device.\n\n**What**\n\nA 403 from the code-session request helper can now report a stale session needing re-login, not just an untrusted device.\n\n**Details**\n\n- The helper always parses the error resource on a 403.\n- Still returns `untrusted_device` as before.\n- Additionally surfaces `session_stale_relogin` when the call site is tagged `elevated_auth`.\n- Replaces the old `classifyUntrustedDevice` option object.\n- The user-facing re-login message itself already existed in 2.1.224.\n\n**Evidence**\n\n`Your session has expired for the trusted-device check. Run \/login to re-authenticate, then retry.`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}