Using Cloud Services, Federation, and Cloud Authentication
As previously discussed, no organization is an island today. In the past, everything an employee used was on systems in the organization’s network that could be part of a trusted domain. Today, pretty much every company in the world leverages SaaS applications outside of their network. This could be to book travel, manage customer relationships, utilize productivity applications, and much more. However, they:
- Don’t exist on the customers network
- Are not joint to the customers domain
This means Kerberos can’t be used. My network is really the useful boundary of my domain. In the early days, this meant every external application would have its own identity database and every user had a separate set of username/password for every application used, which was a nightmare for everyone involved. The user had to maintain a lot of sets of credentials; the user’s local IT administrators have no visibility...