Home › Forums › OS X Server and Client Discussion › Open Directory › PasswordService not playing
- This topic has 4 replies, 2 voices, and was last updated 20 years, 3 months ago by
Anonymous.
-
AuthorPosts
-
October 19, 2004 at 7:49 pm #359586
Matt Wynne
ParticipantNew install of 10.3 Server, updated via Combo 10.3.4 and then a single 10.3.5 update. ODM setup, KDC works, can authenticate from clients as the newly created admin account…all good….however, try adding a user and they are created with Crypt Passwords. Try and change it to OD and you get ‘password server error’. When we looked at the Config under the Inspector, there is no passwordservice entry!
Created a manual entry, using another server as a template, and then you can change the users password to OD but when you press save, you get a ‘plugin error’ in WGM. PasswordService is running, tried hupping it and DS, nada, zip, nothing. Now we’ve done this exactly same thing twice and both are exactly the same. When we just setup one as a vanilla 10.3, setup the OD part and then updated, no problem!
So I guess my question/plea/request is 2 fold:
1. What gets fragged in the ‘update first, configure second’ scenario?
2. How do we fix it?Cheers guys
PS. This has been posted to the ACT forums for those who know, so apologies if you see this twice!
October 21, 2004 at 9:16 pm #359622Matt Wynne
ParticipantDidn’t try using mkpassdb as there didn’t seem to be any password server there!
No juice on the rest though Joel, I’ve had to use NeST to restore an OD password for an admin on a number of occasions but this is very different – the default admin appears to have an OD password but there is no passwordservice entry in the LDAP database! We had to wipe this server to get it going again, and this time used the install,configure, upgrade path and all was well. I just want to make sure that noone else has to go through a day like Tuesday!
October 22, 2004 at 9:49 am #359630Matt Wynne
ParticipantAaaaaarggh! Back to basics – NeST -hostpasswordserver wasn’t working because, for some reason, AUTHSERVER=-NO- was in /etc/hostconfig. Either used NeST -authserver or simply modifing /etc/hostconfig, that then allows NeST -hostpasswordserver …. to do it’s thing!!
Weird but fixed – phewww!
December 29, 2004 at 7:03 am #360265Anonymous
GuestThat is wierd, but I had the same experience and your documenting of it helped me greatly. For the record, the command
NeST -authserver
changes that flag in /etc/hostconfig to AUTHSERVER=-YES- and then running the command
NeST -hostpasswordserver adminuser adminpasswd
adds a trusted admin user to the authservermain database with authority to administer the password server.
Now what to do about LDAP I’m not sure, my admin user isn’t showing up there (but is in the Netinfo D
.MD
-
AuthorPosts
- You must be logged in to reply to this topic.
.
Comments are closed