rpcsec_gss, kadmind service principal, etc.

[Kevin Coffman]

The SEAM kadmind uses the service principal 'kadmin/<f.q.d.n>' rather 
than 'kadmin/admin'.  To be compatible with SEAM, I made changes to use 
'kadmin/<f.q.d.n>' as well.  What do y'all think of this?

The code in the original rpc to deal with multiple possible service 
principal names was removed in our update.  Since I made the above 
incompatible change, I didn't see the need to continue to support the 
older service names.  This is causing problems trying to run the unit 
tests since they run the OV kpasswd program which requires kadmind to 
handle 'kadmin/changepw' as well.  Should I be worrying about this?

K.C.