Red Hat Bugzilla – Bug 1283335
NFSv4 server cannot use sec=krb5 with Microsoft AD as KDC
Last modified: 2016-01-06 09:31:19 EST
Description of problem:
We are setting up a RHEL7 NFSv4 server and a RHEL7 NFSv4 client. We wish to use sec=krb5 for the exports. Our organization uses Microsoft Active Directory, so we have configured sssd on our hosts to use the "ad" backend, and Kerberos (/etc/krb5.conf) to use the Microsoft AD servers as KDCs.
On the NFSv4 server, we run rpc.idmapd, gssproxy, and rpc.mountd.
On the NFSv4 client, we run rpc.idmapd, gssproxy, and rpc.gssd.
When the client attempts to mount a filesystem that is exported from the server, and the client uses sec=krb5, the server responds to the client's AP-REQ attempts by simply closing the TCP connection, and gssproxy logs this debugging output:
Nov 13 15:00:08 server gssproxy: gp_rpc_execute: executing 9 (GSSX_ACCEPT_SEC_CONTEXT) for service "nfs-server", euid: 0, socket: /run/gssproxy.sock
No other log messages appear.
I asked about this issue on the gssproxy mailing list, in this thread:
Simo's suggestion was that I am encountering bug 1213852: there is a bug in the NFS server kernel code that breaks the kernel's interaction with gssproxy. The bug is not fixed yet, but later versions of gssproxy work around this bug.
This suggestion appears to be correct, because when I rebuilt gssproxy-0.4.1-2.fc23.src.rpm for RHEL7 and upgraded to it on the NFS server, the NFS client was able to mount the export from the server with sec=krb5.
Simo indicated that this is a known issue, and a fix is in the works for RHEL7. I am mostly creating this Bugzilla because I could not find any public tracking bug for this issue, and if Simo had not helped me out on the gssproxy mailing list, I doubt I would've figure out the issue.
Version-Release number of selected component (if applicable):
I have lodged the following paid support case with Red Hat to track developments on this bug as our licensed organization is affected: https://access.redhat.com/support/cases/#/case/01541609
I can confirm that gssproxy-0.4.1-7.el7.x86_64 (in RHEL 7.2) contains the workaround for the kernel bug.
Simo, unless you want to leave this bug open until the upstream kernel bug is fixed, feel free to close.
This was a public tracking bug for an issue that has been fixed.