Residents must maintain twenty separate logins for related city services. How should single sign-on be applied?
Select an answer to reveal the explanation.
Short Explanation
Twenty city logins feel like a keyring that never fits the door—SSO can unify them, but only if the front door stays strong. Match authenticator strength to the riskiest app in the circle; a shared four-digit PIN or “SSO means no auth” just paints a target. Renaming the portal without actually federating helps no one.
Full Explanation
SSO reduces password fatigue by allowing one authentication event to unlock multiple relying applications, but assurance must meet the highest sensitivity in the SSO circle. Weak universal PINs or removing authentication after branding changes undermine identity assurance. Cosmetic renaming without technical SSO leaves residents with the same credential burden. Civic portals should pair usability gains with MFA or other assurance controls proportionate to data risk.