Thanks for the response. I am trying to wade through an LDAP paper that I found on IBM's site. Currently, all authentication is done separately: AIX does it's own, Samba does it's own, and an old NT Server is a PDC for the few windows boxes that need to access the network. The majority are just used to support terminal emulation software for the AIX box.
Now however, we are adding PACS. Our PACS web server will sit in a DMZ with a PIX box controlling routing and access to the inside network. The PACS web server will control its' own authentication for the outside physicians.
I was looking for a clean and single control for inside. Perhaps it will need to be a Windows 2000 PDC as the old NT box is going to be deep sixed soon.
Thanks,
Bob Hartung Gordon Messmer wrote:
Gordon Messmer wrote:
To answer your question, you're going to have to inventory all of the servers and services in use at your site, and then research each one to see if they support LDAP or kerberos login. If they all support kerberos, then shoot for that.
To clarify that: Kerberos may be your ideal authentication mechanism, but it probably won't give you all of the features you need. Usually you implement kerberos in conjunction with LDAP.
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
