Not sure what you mean with "Do you still have to do this even if you add the system to AD via a "User" account?" ?
You add the system to AD to be able to create a keytab which is used to verify that you talk to the right kdc during user authentication. It has nothing to do with the ability to login from LOC1.DOM.COM or LOC2.DOM.COM Regards Markus "Chris Penney" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On 5/17/07, Douglas E. Engert <[EMAIL PROTECTED]> wrote: >> Whoses pam_krb5? Russ Allbery's has some extra options that might >> try both realms. > > > On 5/17/07, Markus Moeller <[EMAIL PROTECTED]> wrote: >> You need entries like (assuming that users are uniq over both domains >> and you have more users in LOC1.DOM.COM) >> other auth sufficient pam_krb5 REALM=LOC1.DOM.COM >> other auth sufficient pam_krb5 REALM=LOC2.DOM.COM > > Ah! I see. I used the pam_krb5 that Douglas noted and the pam config > lines you noted and it works basically as intended. > > Do you still have to do this even if you add the system to AD via a > "User" account? > > Thanks! > > Chris > ________________________________________________ > Kerberos mailing list [email protected] > https://mailman.mit.edu/mailman/listinfo/kerberos > ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
