Hmm, yea thats what i figured too, however if i check in the AD,
values for servicePrincipalName is following,
HOST/CLIENT
HOST/client.xx.xxxx.xx
And attribute, userPrincipalName, is following,
nfs/client.xx.xxxx.xx(a)XX.XXX.XX
So you would figure this would work, right ?
kinit -k HOST/CLIENT
kinit -k HOST/client.xx.xxxx.xx
However, it doesn't. It only gives me, Client not found in Kerberos
database while getting initial credentials.
I'm very close to get sssd to work as i want, I've got krb auth backend
to work so the users obtain theirs ticket,
now i want the ldapbind to be kerborized to, but that where am stuck at
the moment.
/Patrik
On 08/05/2010 03:48 PM, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/05/2010 09:43 AM, Patrik Martinsson wrote:
> If i do, kinit -k host/client.xx.xxxx.xx, i get
> kinit: Client 'host/client.xx.xxxx.xx(a)XX.XXXX.XX' not found in Kerberos
> database while getting initial credentials
>
>
That's a server-side issue. It looks to me like you don't have that
service principal set up on AD.
Perhaps you need to use host/CLIENT(a)XX.XXXX.XX instead?
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAkxawR4ACgkQeiVVYja6o6NFMgCdGhAz9fB/K85XO88nI0T1OrmK
TgIAn0J2iyMHt4o9QvzAzHQGy40VsrzB
=NMyJ
-----END PGP SIGNATURE-----
_______________________________________________
sssd-devel mailing list
sssd-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/sssd-devel