The shift to the cloud is underway so IT admins really have two options. While it may seem like a good approach, Centrify’s scope was limited in that it still required Active Directory on-prem to fulfill its purpose. Historically, on-prem identity bridges such as Centrify extended AD to some of these new digital tools, but not all. Resulting from the shift of IT resources in most environments (Windows-based workstations, wired networks, on-prem file servers) to what we have today in our cloud-forward environment (Macbooks, WiFi, and cloud storage) IT organizations are struggling to extend their legacy directory service to these modern IT resources. So, with all of these IT changes, why must the directory remain on-prem and require add ons like Centrify to work with all these resources?
Centrify express for mac mac#
They’re an amalgamation of different types of solutions including G Suite, Office 365, AWS and GCP, Mac and Linux machines, web applications such as Slack, Github, Salesforce, cloud and physical file servers ( NAS devices, Samba file servers, and Box™) and many other types of IT resources. Do we want to continue to leverage on-prem hardware and its expenses when the industry is shifting to the cloud? No longer are IT networks based on just Microsoft Windows. What we should really be asking when we attempt to define Centrify’s now defunct role is more of a question about the right approach to identity management in the cloud era. Idaptive, on the other hand, looks to follow the traditional first generation IDaaS path that has been paved by companies such as Okta and OneLogin. It seems as though the current incarnation of Centrify will keep the privileged access management components (Linux and network infrastructure authentication). Centrify was essentially an add-on to on-prem Active Directory infrastructure. Previously, the Centrify Express product extended legacy, on-prem Microsoft Active Directory identities to non-Windows resources such as Mac and Linux systems as well as web applications. We use the past tense to say that Centrify was an identity bridge because the product recently faced EOL, and Centrify split into two companies- Idaptive and Centrify. In short, Centrify was an identity bridge. In web searches targeted at discovering a way to extend AD, Centrify comes up quite a bit, so it’s important to understand what their product does. With IT organizations looking to connect their non-Windows resources to Microsoft Active Directory, one question comes up quite often: what is Centrify?
0 kommentar(er)
