Files
zeekay cf8e004212 device: the link opens on the application's sign-in origin; a person can refuse
The verification_uri and verification_uri_complete a device is handed are on the
origin of the application's signinUrl when the operator has configured that origin
as a sign-in origin of the request's issuer (IAM_FEDERATION_ORIGIN_MAP), and on the
issuer otherwise. The application says; the operator decides, so a tenant-written
signinUrl can only select among configured origins and an origin of another brand is
refused as the boot check refuses a map that would send one there. Only the origin
is taken. The issuer, discovery and the JSON endpoints do not move.

signinUrl is declarable: the upsert takes it (a pointer: omitted preserves, "" clears,
anything but an https URL is refused) and the provision document carries it per app
(`signin:`).

A person can refuse: POST /v1/iam/login {type:"device", userCode, deny:true} on the
approval's own seam (session, same-origin JSON, the account the page showed, the
tenant boundary). The device's next poll is access_denied once and the code is dead
after; approve, look-up and a second refusal find it spent (one `pending`).

device/info names the account an approval would be made as, so the page returns it
as the approval's loginHint.

Claude-Session: https://claude.ai/code/session_015XYKLnjAuGqkk4ssA1Jusy
2026-11-08 13:58:13 -08:00
..