<br><br><div><span class="gmail_quote">On 7/19/06, <b class="gmail_sendername">Cleber P. de Souza</b> <<a href="mailto:cleberps@gmail.com">cleberps@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi list.<br><br>Maybe this could be off-topic but here I think many have used OpenLDAP<br>to unify yours authentication needs, allowing an unique username and<br>password for all the corporate applications.<br>My doubt is, which rules do you use to split all the user levels so
<br>that one user could be allowed to access app A but isn't allowed to<br>access app B (think this about many apps)?<br>Have you been using OU's to split user by app and copying them to each<br>app that them must access? Using posix groups and filtering users by
<br>filters on each app?</blockquote><div><br>
As I see it, you should be creating as many OU's as user categories
-roughly one per app. Smack each user into as many OUs as needed, then
filter on OUs AND on POSIX groups as you see fit.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks by the help.<br><br>--<br>Cleber P. de Souza<br>_______________________________________________
<br>CentOS mailing list<br><a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</a><br></blockquote></div><br>
<br clear="all"><br>-- <br>Eduardo Grosclaude<br>Universidad Nacional del Comahue<br>Neuquen, Argentina