Question 440
A field device has limited input and needs its operator to approve application access on a trusted second screen. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Consider a supported device authorization flow only for an appropriate constrained client with secure user verification. Verification: Test device/user codes, verification URI, polling interval, expiration and consent. Boundary: Device authorization is not a shortcut for unattended server access or bypassing user approval” addresses the access-design responsibilities in a field device has limited input and needs its operator to approve application access on a trusted second screen Test against test device/user codes, verification URI, polling interval, expiration and consent; device authorization is not a shortcut for unattended server access or bypassing user approval.
Incorrect Answers
“Action: Use a dedicated least-privileged app execution identity and restrict access at OAuth, object, field and record layers. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. Boundary: Device authorization is not a shortcut for unattended server access or bypassing user approval” may apply to a related identity task, but it does not establish test device/user codes, verification URI, polling interval, expiration and consent for a field device has limited input and needs its operator to approve application access on a trusted second screen The controlling boundary is: Device authorization is not a shortcut for unattended server access or bypassing user approval.
“Action: Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior. Verification: Test device/user codes, verification URI, polling interval, expiration and consent. Boundary: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” may apply to a related identity task, but it does not establish test device/user codes, verification URI, polling interval, expiration and consent for a field device has limited input and needs its operator to approve application access on a trusted second screen The controlling boundary is: Device authorization is not a shortcut for unattended server access or bypassing user approval.
“Action: Consider a supported device authorization flow only for an appropriate constrained client with secure user verification. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” may apply to a related identity task, but it does not establish test device/user codes, verification URI, polling interval, expiration and consent for a field device has limited input and needs its operator to approve application access on a trusted second screen The controlling boundary is: Device authorization is not a shortcut for unattended server access or bypassing user approval.