<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think you problem is FreeNAS and not IPA itself. In FreeNAS 10 they will have built in IPA functionality.<br class=""><div><blockquote type="cite" class=""><div class="">On Oct 8, 2016, at 5:47 PM, Arthur Morales Sampaio <<a href="mailto:amostech@gmail.com" class="">amostech@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="gmail_msg">Good morning, my name is Arthur and I am working on the integration of FreeIPA and NFSv4 mounting for home directory sharing for authenticated users.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">This is the first time I am doing this so the problem could be simple. It's been already a week that I have been struggling with this and I don't know where else to ask for help. I have read pretty much everything that is to be read online regarding Freeipa integration.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Here is my scenario:</div><div class="gmail_msg">- FreeIPA server 4.2.0 - Centos7</div><div class="gmail_msg">- FreeNAS (NFSv4 server) 10 - FreeBSD (bundled with FreeNAS)</div><div class="gmail_msg">- Client Ubuntu 16.04. Installed IPA client using ipa-client-install and imported LDAP credentials. Kerberos login is working properly I can log into the machines using IPA users. But can't mount NFS4 using sec=krb5 option.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I have a functional FreeIPA server with Kerberos authentication working properly. But I can't get NFSv4 authenticated to work in freeipa-clients. </div><div class="gmail_msg"><br class=""></div><div class="gmail_msg">Following is the error that I am getting:</div><div class="gmail_msg"><br class=""></div><div class="gmail_msg"><span id="inbox-inbox-docs-internal-guid-82a9b2e9-a6e0-3d27-8f74-f88eb2d11c79" class=""><img width="731px;" height="96px;" src="https://lh4.googleusercontent.com/yXV6gyXdgVddM3uVWbnR2aJcoALS-X4Ei5-RJuVKCeaDxX8SaYzxC-X6NsMOrIzrMl83e4inYQCnGuOalyABl6OeOI3KXeI2WvVuCdD3md0lVOAe0dVu4dv5P87sXqtL-nh8h5BtqBY" class=""></span><br class=""></div><div class="gmail_msg"><span class=""><br class=""></span></div><div class="gmail_msg"><span class="">I know that this might not be enough detail for me to get help for this problem. But the thing is that I don't know how to enable a more verbosity functionality for this.</span></div><div class="gmail_msg"><span class=""><br class=""></span></div><div class="gmail_msg"><span class="">The desired behavior would be to create mounts for home directories of users and enable kerberos security to mount them. Meaning that I need only the owners to be able to mount them. </span></div><div class="gmail_msg"><span class=""><br class=""></span></div><div class="gmail_msg">This is something that is very confusing for me. Wouldn't I be required to somehow pass to the mount command the username or any credentials of the kerberos user just so the NFS server would know <b class="">WHO</b> is trying to mount the directory?</div><div class="gmail_msg"><br class=""></div><div class="gmail_msg">I really exhausted my resources in trying to fix this issue. </div><div class="gmail_msg"><br class=""></div><div class="gmail_msg">Does FreeIPA work with NFSv4? </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I sincerely appreciate your help on this one.</div><div class="gmail_msg"><br class=""></div><div class="gmail_msg">Best regards,</div><div class="gmail_msg">Arthur</div></div></div>
-- <br class="">Manage your subscription for the Freeipa-users mailing list:<br class=""><a href="https://www.redhat.com/mailman/listinfo/freeipa-users" class="">https://www.redhat.com/mailman/listinfo/freeipa-users</a><br class="">Go to http://freeipa.org for more info on the project</div></blockquote></div><br class=""></body></html>