Home › Forums › OS X Server and Client Discussion › Mail › Leopard server and Tiger client
- This topic has 1 reply, 1 voice, and was last updated 18 years, 10 months ago by
robinson.
-
AuthorPosts
-
January 13, 2008 at 7:11 pm #371106
robinson
ParticipantI have a Leopard Server (10.5.1) running with Tiger clients (10.4.11). I configured mail accounts with Kerberos Version 5 (GSSAPI). I think when i log in with a network user I get a kerberos ticket but when I start Mail it asks to enter my kerberos password again. How to avoid that?
January 14, 2008 at 2:34 pm #371112robinson
ParticipantMacTroll wrote:
First, ensure that you’re getting a ticket.
klist or the Kerberos.app will show you this.
Now I see. I thought if a user logs in he gets a kerberos ticket, isn’t it? Then how to ensure that my users get their tickets on log in?
Now I checked slapconfig.log and found
2007-12-07 01:04:15 +0100 – sso_util command output:
Contacting the directory server
Creating the service list
Creating the service principals
WARNING: no policy specified for cifs/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for ldap/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for xgrid/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for vpn/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for ipp/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for xmpp/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for XMPP/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for host/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for smtp/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for nfs/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for http/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for HTTP/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for pop/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for imap/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for ftp/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for afpserver/server.asam.private@SERVER.ASAM.PRIVATE; defaulting to no policy
Creating the keytab file
Configuring services
WriteSetupFile: setup file path = /temp.X5rV/setup2007-12-07 01:04:15 +0100 – command: /sbin/kerberosautoconfig -f /LDAPv3/127.0.0.1 -u -v 1
2007-12-07 01:04:15 +0100 – command: /usr/sbin/mkpassdb -kerberize
2007-12-07 01:04:15 +0100 – mkpassdb command output:
WARNING: no policy specified for server.asam.private$@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for root@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for diradmin@SERVER.ASAM.PRIVATE; defaulting to no policy
add_principal: Principal or policy already exists while creating “diradmin@SERVER.ASAM.PRIVATE”.
WARNING: no policy specified for disabled-slot-0x1@SERVER.ASAM.PRIVATE; defaulting to no policy
WARNING: no policy specified for server.asam.private$@SERVER.ASAM.PRIVATE; defaulting to no policy
add_principal: Principal or policy already exists while creating “server.asam.private$@SERVER.ASAM.PRIVATE”.
WARNING: no policy specified for root@SERVER.ASAM.PRIVATE; defaulting to no policy
add_principal: Principal or policy already exists while creating “root@SERVER.ASAM.PRIVATE”.
WARNING: no policy specified for diradmin@SERVER.ASAM.PRIVATE; defaulting to no policy
add_principal: Principal or policy already exists while creating “diradmin@SERVER.ASAM.PRIVATE”.
WARNING: no policy specified for disabled-slot-0x1@SERVER.ASAM.PRIVATE; defaulting to no policy
add_principal: Principal or policy already exists while creating “disabled-slot-0x1@SERVER.ASAM.PRIVATE”.How to correct this?
-
AuthorPosts
- You must be logged in to reply to this topic.