On Jul 30, 2014, at 3:15 AM, Lloyd Parkes <[email protected]> wrote:
> The solution I've used the past is really quite heavyweight, so apologies in > advance. I used Oracle Virtual Directory to create the LDAP entries on the > fly based on information in backend LDAP (or other) systems. Since the LDAP > entries are built on the fly, you should be able to arrange it so that the > production cluster sees different information for the web developer than what > the developer's personal dev machines see. I haven't played this particular > game with OVD, but this technology does seem to be available. > That’s honestly not a solution that had crossed my mind. Some convoluted overlays and such could do exactly what I want once I get around to figuring out the various rewriting bits. I’ll have to look into the OpenLDAP rewrite support. Now, because I may be able to swing something similar at $DAYJOB (where I’m saddled with both Oracle Solaris 11 (in addition to Linux and AIX) and AD as the LDAP backend (ugh!)), anybody have any ideas how to accomplish this when AD is the backend? :-) -c ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
smime.p7s
Description: S/MIME cryptographic signature
