Hello Roland, I see, the client-side approach. Did not think far enough. Your suggestion works like a charm. Thank you. Still I need the aliases, as in phpMyEdit they get resolved by apache. Now both solutions do what they are expected to.
Regards, Thomas From: Roland Gruber [mailto:[email protected]] Sent: Donnerstag, 20. September 2018 08:08 To: [email protected]; Meller, Thomas Cc: Tehrani, Ulrich Subject: Re: [Lam-public] Including subordinate identity pools by alias Hi Thomas, instead of using aliases you could assign a group of names to the QA users and team leads. Then use dc=t-systems,dc=ch as login search suffix for the QA profile. Best regards Roland Am 19. September 2018 17:51:26 MESZ schrieb [email protected]: I have the need to separate two different types or users: 1. Login-accounts (need access to servers) 2. Administrative accounts (no technical use, only needed for QA reasons) Type 2 should not get mixed with type 1. The reason being, security auditors checking our company security should not confuse these and keep their eyes focused on type 1 accounts only. So I created a different subtree to separate these types technically: 1: ou=css,ou=oss…..ou=unix,ou=users …
_______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
