<div dir="ltr">A really good point however I'm fortunate enough that the only items authentication are applications. I agree with you also that it's a bit of a Pandoras box; I've decided that it's best to leave the systems in default state and use a tool like PWM for this self service component. </div><br><div class="gmail_quote"><div dir="ltr">On Wed, Mar 9, 2016 at 12:37 AM Petr Spacek <<a href="mailto:pspacek@redhat.com">pspacek@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 8.3.2016 15:29, Matt Wells wrote:<br>
> For my use case it is. Essentially the system will be application auth for<br>
> separate groups that have no need to know of one another, almost a<br>
> multi-tenant mode. I wanted to expose a 'self service' url. I've found a<br>
> community ipa portal for password resets and perhaps that with slight<br>
> changes can resolve this. I understand why it's that way but had hoped to<br>
> be able to apply a bit more of an ACI; I've been able to ratchet the<br>
> accounts down to just this one item thus far by restricting access to<br>
> attributes. I appreciate the response and if / when I find a solution I'll<br>
> post it for anyone else that would require it.<br>
<br>
Be sure you fully think though your use cases and understand the implications.<br>
<br>
E.g. if the LDAP is used by unix clients, locking it down to one user or group<br>
may prevent clients from translating UIDs to names and vice-versa, prevent<br>
resolving group membership etc. That would certainly break things.<br>
<br>
In this case you might want to craft ACI which exposes POSIX attributes only<br>
and nothing else or so.<br>
<br>
Again, think about it :-)<br>
<br>
Petr^2 Spacek<br>
<br>
> On Mon, Mar 7, 2016 at 11:05 PM, Prashant Bapat <<a href="mailto:prashant@apigee.com" target="_blank">prashant@apigee.com</a>> wrote:<br>
><br>
>> A user will be able to list all other users and be able to read their<br>
>> attributes. But will not be able to change anything.<br>
>><br>
>> Is that an issue ? I mean on a Linux box you can read /etc/passwd file<br>
>> which has info about all users on that box. This doesn't cause issues.<br>
>><br>
>> On 8 March 2016 at 03:03, Matt Wells <<a href="mailto:matt.wells@mosaic451.com" target="_blank">matt.wells@mosaic451.com</a>> wrote:<br>
>><br>
>>> Hi all, I had a quick question. I swear I had this before but that could<br>
>>> be the voices telling me it's true....<br>
>>> A normal user is logging into IPA (4.2.0) and filling in their phone<br>
>>> number and info no problem. However when that user clicks on accounts<br>
>>> above they are then able to peruse the entire directory and all the other<br>
>>> user accounts.<br>
>>> I'm trying to remove that but for the life of me can't recall the ACI or<br>
>>> where that may be.<br>
>>><br>
>>> I really appreciate it, I'll continue to search through the previous<br>
>>> questions and if I find it before a reply will mark this closed with the<br>
>>> link.<br>
>>> Thank you all -<br>
>>> Wells<br>
<br>
--<br>
Manage your subscription for the Freeipa-users mailing list:<br>
<a href="https://www.redhat.com/mailman/listinfo/freeipa-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/freeipa-users</a><br>
Go to <a href="http://freeipa.org" rel="noreferrer" target="_blank">http://freeipa.org</a> for more info on the project<br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><span>Matt Wells</span><br><span>Chief Systems Architect</span><br><span>RHCA, </span><span>RHCVA - #110-000-353</span><br><span>(702) 808-0424</span><br><a>matt.wells@mosaic451.com</a><br><span> Las Vegas | Phoenix | Portland Mosaic451.com </span><br><span>CONFIDENTIALITY NOTICE: This transmittal is a confidential communication or may otherwise be privileged. If you are not intended recipient, you are hereby notified that you have received this transmittal in error and that any review, dissemination, distribution or copying of this transmittal is strictly prohibited. If you have received this communication in error, please notify this office, and immediately delete this message and all its attachments, if any.</span><br></div>