what's next for nfs v4 and AD?
Par blindaue le samedi, juin 17 2006, 08:44 - kerberos - Lien permanent
In the effort to easily deploy nfs v4 with AD, here my following steps
Take a computer, alone just installed :)!!
- install samba and kerberos
urpmi samba-client samba-winbind krb5-workstation pam_krb5 - configure
- /etc/samba/smb.conf:
workgroup = DPTINFO
realm = DPTINFO.URS.LOCAL
security = ads
password server = *
use kerberos keytab = yes - /etc/krb5.conf:
[libdefaultsdefault_realm = DPTINFO.URS.LOCAL[realmsDPTINFO.URS.LOCAL = {kdc = myad.u-strasbg.fr:88admin_server = myad.u-strasbg.fr:749default_domain = u-strasbg.fr}[domain_realm.u-strasbg.fr = DPTINFO.URS.LOCAL
- /etc/samba/smb.conf:
- Join the AD domain:
- Do it:
$ su -Password: ******
# kinit Administrator
Password for Administrator@DPTINFO.URS.LOCAL: ******
# net ads join
# - Verify :
# net ads status
... Lot of stuff...
You should see several //servicePrincipalName//, withHOST/FQDN,HOST/hostname,CIFS/FQDNandCIFS/hostname. If your domain name (DNS) isn't your REALM (AD), you should see two FQDN, I see for my example:HOST/ibis.u-strasbg.frandHOST/ibis.dptinfo.urs.local
- Do it:
- On a DC computer with installed supports tools, verify that your linux box is ready, in a cmd.exe box:
$ setspn -L ibis
HOST/ibis.u-strasbg.fr
HOST/ibis
HOST/ibis.dptinfo.urs.local
CIFS/ibis.u-strasbg.fr
CIFS/ibis
CIFS/ibis.dptinfo.urs.local - Add the SPN for nfs:
$ setspn -A nfs/ibis ibis
Registering ServicePrincipalNames for CN=ibis,CN=Computers,DC=DPTINFO,DC=URS,DC=LOCAL
nfs/ibis.u-strasbg.fr
Updated object
(add nfs/fqdn too) - You can verify with
setspn -L ibisthat the SPN has been added - Try to you your new SPN on the linux box:
# kvno nfs/ibis.u-strasbg.fr
nfs/ibis.u-strasbg.fr@DPTINFO.URS.LOCAL: kvno = 0
and after that, verify that the ticket is valid:
# klist |grep nfs
06/17/06 06:48:07 06/17/06 13:09:35 nfs/ibis.u-strasbg.fr@DPTINFO.URS.LOCAL
Here come the problem: it seems that we can't use this SPN for rpc.gssd. What seems to be more confusing is that the keytab which can be generated on windows doesn't seem to be valid:
# kinit -k
kinit(v5): Client not found in Kerberos database while getting initial credentials
# klist -k -e
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
--
1 nfs/ibis.u-strasbg.fr@DPTINFO.URS.LOCAL (DES cbc mode with CRC-32)
Commentaires