[OpenAFS] pam errors login... win2003AD krb5 server

[Russ Allbery]

Lars Schimmer <l.schimmer@cgv.tugraz.at> writes:

> I changed krb5 server from MIT to Win 2003 AD (on another PC).  So I
> only changed the name of the krb5 server in the krb5.conf and rebooted.
> LogIn as root and kinit user /aklog obtained me tickets/tokens.  Login
> via gdm/pam doesn=B4t do well (it works with MIT krb5 server, not with
> Win2003AD). Syslog tells me this:

> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: pam_sm_acct_mgmt:
> entry (0x8000)
> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: skipping
> non-Kerberos login
> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: pam_sm_acct_mgmt:
> exit (success)
> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: pam_sm_setcred:
> entry (0x2)
> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: no context found,
> creating one
> Jun  8 09:30:01 testpc CRON[5056]: (pam_krb5): none: ignoring root user

Those syslog messages are all from cron running session hooks before
jobs.  We'd need to see the log messages from gdm to figure out what's
wrong with gdm.

--=20
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>