Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Kerberos error in Console whenever I log into my Mac from the screensaver

0dev

0dev

macrumors 68040
Original poster
Dec 22, 2009
3,947
24
127.0.0.1
When my Mac wakes up, it asks me for a password. When I type the password in correctly and it logs me in, I notice it creates this error on the Console:

Code: 
loginwindow[32]	in pam_sm_authenticate(): Failed to determine Kerberos principal name.

I did some research and could only find stuff about SSH, but notice this is just the standard loginwindow. I'm not running a server and I have SSH turned off. From what I can work out, though, this error is meant to represent a failed login attempt. But then why does it come up on successful login attempts? Is there any reason for this? Is this just what's meant to happen?

I know it's probably nothing but still, I find myself quite curious.
 
0dev said:
When my Mac wakes up, it asks me for a password. When I type the password in correctly and it logs me in, I notice it creates this error on the Console:

Code: 
loginwindow[32]	in pam_sm_authenticate(): Failed to determine Kerberos principal name.

I did some research and could only find stuff about SSH, but notice this is just the standard loginwindow. I'm not running a server and I have SSH turned off. From what I can work out, though, this error is meant to represent a failed login attempt. But then why does it come up on successful login attempts? Is there any reason for this? Is this just what's meant to happen?

I know it's probably nothing but still, I find myself quite curious.
Click to expand...

You shouldn't be concerned about this. Kerberos is part of the login process. When logging in, the computer tries several things until it finds one that works. Seeing that you are not using Kerberos to log in (but the local directory), it can't find your user principal, so that's probably why this is happening.

Anyway, that's what I think.
 
Last edited:
jackhdev said:
You shouldn't be concerned about this. Kerberos is part of the login process. When logging in, the computer tries several things until it finds one that works. Seeing that you are not using Kerberos to log in, it can't find your user principal, so that's probably why this is happening.

Anyway, that's what I think.
Click to expand...

Makes sense, thanks :)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back