A SaaS HR platform will authenticate city employees via the city’s identity provider. What must the architect manage for cloud federation?
Select an answer to reveal the explanation.
Short Explanation
When SaaS HR plugs into the city IdP, you are wiring trust—not inventing a second password pile. Lock down federation trust, check endpoints and signing keys, and ration attributes. Cleartext SaaS passwords, letting the vendor IdP the whole city, or skipping validation are cloud federation own-goals.
Full Explanation
Cloud federated identity requires a governed trust relationship between the municipal IdP and the SaaS relying party, including validated endpoints, signing keys, and scoped attribute release. Creating parallel cleartext SaaS passwords reintroduces credential sprawl. Allowing the SaaS to become an unconstrained IdP for internal systems inverts trust boundaries. Skipping cryptographic validation assumes integrity that must be verified continuously.