Some municipal apps remain on-premises while others are SaaS, yet leadership wants one coherent identity strategy. Which approach fits hybrid federation?
Select an answer to reveal the explanation.
Short Explanation
Hybrid identity is one conductor for two orchestras—on-prem and SaaS—following the same IdP sheet music. Keep policies and lifecycle unified where you can. Forever silos, double passwords everywhere, or orphaning cloud accounts when roles change break the hybrid story.
Full Explanation
Hybrid federated architectures center authentication on a governed identity provider (or tightly synchronized providers) so on-premises and cloud applications apply consistent authentication, authorization, and lifecycle rules. Permanent silos and mandatory per-app passwords recreate the fragmentation federation is meant to solve. Failing to synchronize or deprovision cloud identities when roles change leaves orphaned access. Coherent hybrid design balances app hosting diversity with unified IAM policy.