A library multi-tenant SSO setup lets a user from one tenant open another tenant's account context after a misconfigured identity mapping. What theme should the tester frame?
Select an answer to reveal the explanation.
Short Explanation
SSO is supposed to be a trusted handshake, not a mix-up at coat check. When identity mapping is wrong, one tenant can wander into another's locker. Call the class — broken auth or SSO misconfig — without needing a vendor deep-dive.
Full Explanation
Single sign-on misconfigurations can confuse tenant or user identity assertions and produce unauthorized cross-account access. Testers should validate audience restrictions, tenant binding, session handling, and logout behavior at a conceptual level. Framing the issue as broken authentication or SSO misconfiguration is appropriate without specializing in one IdP product. TLS cipher or DNSSEC distractors miss the identity-mapping failure.