{"version":"2.1.225","anchor":"untrusted-device-credential-rejection-surfaces-as-a-rejectio","canonical_anchor":"untrusted-device-credential-rejection-surfaces-as-a-rejectio","heading":"Untrusted-device credential rejection surfaces as a rejection","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/untrusted-device-credential-rejection-surfaces-as-a-rejectio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Untrusted-device credential rejection surfaces as a rejection\n\nAn untrusted device now gets a clear rejection instead of a silent failure and endless retries.\n\n**What**\n\nRemote credential fetch retries once through a new device-attestation path, and an untrusted_device result without the relevant capability now returns a terminal rejection instead of a bare null.\n\n**Details**\n\n- The rejection carries `reason: \"request_rejected\"` with status 403 and is marked terminal, so callers stop retrying.\n- OAuth-rejected results are now passed through to the caller rather than swallowed.\n- The enabled state of the surrounding path could not be resolved from the build.\n\n**Evidence**\n\n`{ terminal: !0, reason: \"request_rejected\", status: 403 }`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}