Unable to authenticate for Kerberos Login.
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have a 10.4.1 server running as an open directory master with all open directory services running.
I have setup AFP to authenticate with any method: standard or kerberos.
Every time I try connect via AFP I get a kerberos login screen but it never authenticates successfully. If I cancel the login request the regular afp login option appears and the authentication used before works here.
Can anyone shed some light on why there seems to be two separate sets of passwords as Kerberos must be looking for something else.
Many Thanks
Mike
13 replies
Sign in or join Beachball Help to reply.
- 0
Leland Wallace ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
If the client is bound to the OD master, you should be automatically getting a Kerberos TGT on login & should never see the Kerberos login dialog.
Since you are seeing the Kerberos login, I'll assume that the client is not bound to the OD master. Your Kerberos username is your shortname, rather than your longname. Try entering your shortname into the Kerberos login dialog.
Leland
- 0
Mike Kassar ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks Leland,
That is what is quite weird. I have bound the machine to the OD Master successfully yet the logIn prompt still appears.
What is even weirder is that from the kerberos login I can actually change my password thus telling me that I am using the correct credentials.
Thus I do get a ticket but for some odd reason the kereberos login does not go through. After I get the ticket, I get a window with error that the connection failed, unknown user, inccorrect password, or login disabled.
I have tried logging into the directory domain as well as a local login with the same error.
Any more ideas would be much appreciated,Thanks
- 0
Leland Wallace ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
You can test the binding from a users point of view by (after login) opening terminal (or the kerberos app) and checking to see if the user has a tgt.
You can check that the user has a Kerberos Auth Authority using WGM to inspect the user record [go to preferences & check Show "All Records" tab and inspector]
What version of Mac OS X Server are you using?
Try turning on all the logging options in the AFP Server & see what messages are returned when the problem user loggs in.
Do you have any users that can log in via Kerberos?
Leland
- 0
Mike Kassar ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Leland,
I have ensured I get a TGT and a Kerberos Authority thanks to your advice, but all looks good. I am running Tiger Server 10.4.1 and connecting from Tiger 10.4.1 client via AFP with kerberos authentication:
Here is the logged error and it may say a lot but I cannot figure it out:
Jul 11 2005 10:55:34 KERBEROS-LOGIN-CHECK: user {0x42baca38353ef5cc0000000f0000000f, mkassar} is in good standing.
Jul 11 2005 10:55:34 QUIT: {no user} disconnected.
Jul 11 2005 10:55:34 KERBEROS-LOGIN-CHECK: user {0x42baca38353ef5cc0000000f0000000f, mkassar} authentication succeeded.
Jul 11 2005 10:55:34 QUIT: {no user} disconnected.Thanks again,
Mike
- 0
Leland Wallace ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
That looks like the password server log entry for when the user gets a tgt.
You should also look at the kdc log.If you open the Kerberos app (or use klist on the command line) after a mounting attempt, do you see a ticket for the afp server? (afpserver/fqdn@REALM)
One could also turn on the AFP client logging as follows:
as root, edit /etc/syslog.conf so that the entry on the second line that reads "kern.debug" changes to "*.debug". Then restart syslogd e.g. kill -HUP pid
ofsyslogdretry your test, there should be gobs of info in /var/log/system.log
It is possible that the afp server is not properly kerberized (and not sending the correct principal name) or there is some problem with the credentials cache on the client.
Leland
- 0
Sean Lazar ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Mabye this is fixed in Server 10.4.2. I know that Single sign on for Active Directory accounts is fixed, tested it myself just now! 🙂
- 0
Mike Kassar ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Happy to report that the issue is fixed for me in 10.4.2.
Though I had to rekerberize the server and did this the fasted way, by recreating a new OD Database.Only have a handful of users so it was easy.
Mike
- 0
Nathaniel Madura ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
One quick question, I think I am having a similar problem.. how do I "rekerberize" the server?
- 0
StealthRocket ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm also looking for information on how to do this without rebuilding the OD master.
- 0
Leland Wallace ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Before you try to "rekerberize" check to see if the service principals are properly formed (there is a DNS issue that could have messed up the service principals that get created when the server gets kerberized).
as root on the OD Master, run
kadmin.local -q listprincslook in the output for service principals of the form service/@REALM.
If you see any of them you will want to reissue the sso_util configure command to create the proper principals (service/fqdn@REALM)
sso_util -r REALM -f /LDAPv3/od.master.fqdn -a admin -p password -v 1 allThis should reconfigure the afp server & the other kerberized services.
then you can go in with kadmin & remove the bad principals.HTH
- Leland - 0
Scott Mitchell3 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm searching discussions on a related issue - LDAP authentication never succeeds. I've come across the advice to list principals in a number of threads, and have confirmed that I do not have any principals set up for services, only users.
But here's what happens when I try to configure the services using the command you've listed:
Contacting the directory server
Creating the service list
Creating the service principals
kadmin: Client not found in Kerberos database while initializing kadmin interface
SendInteractiveCommand: failed to get pattern
(this repeats for each service)...Any suggestions?
- 0
Leland Wallace ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
try running kadmin alone e.g.
kadmin -p admin@realmand see if that succeeds.
If it fails, look at your /Library/Preferences/edu.mit.Kerberos fileHTH
- Leland - 0
Huw Jenkins2 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm having the same problems only I succeed at this point...
Here's a brief overview of my log files:
LDAP log:
Nov 28 15:03:33 server slapd[58]: SASL [conn=411] Failure: GSSAPI Error: Miscellaneous failure (Key version number for principal in key table is incorrect)
Here an interesting one:
Password Service Replication:
Nov 28 2005 15:43:32 The remote replica list has 1 parent and 1 replica.
Nov 28 2005 15:43:32 Updating the list of replicas. There is 1 parent and 1 replica in the list.
Nov 28 2005 15:43:32 syncfile: /var/db/authserver/apsSyncFi1133192612.627750
Nov 28 2005 15:43:32 sent 1 record, accepted 0, superceded 0
Nov 28 2005 15:43:32 No Kerberos records to update
Nov 28 2005 15:43:32 DoSync: the next replication will occur on 11/29/2005 at 12:00:00 AMIt seems that users who have an old Kerberso ticket can log on to AFP via Kerberos but new users cannot...