Why are Multiple Directories Deployed and Virtual Directories Ignored (Part 2 of 3)
So why do customers need multiple directories? I see two major reasons for customers deploying multiple directories.
- Separation of Operations – this is the most popular reason and is easily attributed to security or most companies deal with. The most typical reason I see is when a customer has an internal and external.
- Internal Politics – Politics that drive more complex deployments can be caused by internal organization politics or external global or national politics. My opinion is that there is a better chance that internal politics that at first seem to demand additional directories will fad overtime.
- External Politics – Some countries demand security separation for specific industries such as defense or finance and in most cases this is mandatory and probably won’t change soon. Unfortunately, this situation is pretty close to #1 Separation of Operations and so using
- “A vendor requires it” – this is the least popular because people want fewer directories and so they avoid vendors who demand such things! This is really the very-very worst reason to deploy new infrastructure I suggest anyone being asked to do this – think twice.
Even though customer directory deployments comes in all shapes and sizes there are a few common threads that I see and how those correlate to some new technologies that are starting to be adopted. (More on this in a couple of days)
In part 3 I will go through why I see Virtual Directories being ignored.
2 Responses Leave a comment
Another (inline with #1) is when a company has AD and LDAP. We have both that and RDBMS based auth systems, and are interested in how VD technology could be used to provide a more streamlined approach.
Hi jeff,
VD technology can provide you with a single unified and robust authentication source for your applications. and can even provide each application with a different view if required.