Intigrating Solaris with Active directory

I am currently looking to intigrate a bunch of Solaris
9 systems with Active
directory. My current line of
thinking is to use Kerberos to authenticate
users.
Which leaves the issue of how to provide a name
service (i.e shared
username/uid group/gid mappings).
Currently we use NIS+ and particularly the
@netgroup
syntax to restrict access to machines. We want to
move away from
this as Sun keep warning of its demise.
Is there any way to do this with LDAP
as a name
service. Are there other ways of doing this with
lesser name
services.

Any other suggestions would be most welcome. Summary
to be
provided if appropriate.

Regards
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • Re: Windows GSSAPI ssh connection via cross-realm authentication problems
    ... I think you misunderstand the role of Kerberos here. ... If the SSH service is in realm ... The non-Windows KDC needs to trust any user ... kdcadmin user's home directory and that one can authenticate just fine. ...
    (comp.protocols.kerberos)
  • Re: Kerberos machine authentication - apparent authentication fail
    ... >From what I can tell the kerberos failure shown in netdiag does not always ... mean that kerberos authentication is not being used. ... computer for logon events and the domain controller for account logon events ... > authenticate with K after initial failures. ...
    (microsoft.public.windows.server.security)
  • Re: Solaris Pam_krb5.so.1 problem after installing MIT 1.6.3
    ... I am actually using kerberos for authenticating logins through ssh. ... Because I had no DNS entry for this Solaris box I was getting the ... The Samba configure script was bombing ... Since I upgraded Samba and added the DNS entry I can successfully login ...
    (comp.protocols.kerberos)
  • RE: Solaris Pam_krb5.so.1 problem after installing MIT 1.6.3
    ... I am actually using kerberos for authenticating logins through ssh. ... This is indicative of DNS issues according to the Solaris Kerberos ... The Samba configure script was bombing ... Since I upgraded Samba and added the DNS entry I can successfully login ...
    (comp.protocols.kerberos)
  • OpenSSH, Kerberos, GSSAPI, and windows clients
    ... My FreeBSD is happy authenticate from itself to itself via its own KDC. ... backport of Simon Wilkinson's gssapi patch. ... downloaded WinSCP 375 beta which claims to have SSH2/MIT Kerberos V ...
    (SSH)