> why would someone who has adopted a decoupled application infrastructure decide that their domain controller should be coupled? You'd really only want the cu

> why would someone who has adopted a decoupled application infrastructure decide that their domain controller should be coupled? You'd really only want the current appliance if you don't have the in house staff to assemble/amalgamate an equivalent setup. My pitch would be that tight coupling enables major security benefits in the implementation: * rapidly propagate policy updates (eliminate race conditions caused by changes slowly propagating across SaaS vendors.) * simpler modules with fewer features, less attack surface * rich context in logs (even spoofed packets have a cryptographically verified source) * coherent security controls > something competitive with Okta I could imagine building the product into "the Okta of on-prem".