1) what is the overhead of doing strong authentication between
peer-to-peer processes in an IBM mainframe, and IBM UNIX environment,
5% 10%, 15%? Are there any hardware solutions, that could take over
the load?
2) This is an LDAP environment. An assumption is that LDAP is better,
stronger, more secure than active directory etc. Is there some reason
that Kerberous isn't compatable with LDAP? Does LDAP have it's own
strong authentication element that removes the need for Kerberous?
Is it possible to create a VPN tunnel using LDAP alone, or do you need
SSH or some other tool for this? Can you do single signon with SSH, or
does this cause overhead for each process to process virtual circuit?
I think I know the answers to some of these, but I'm trying to get all
the info I can. Any other ideas on how to reduce the overhead load of
doing strong authentication?
Re: Directory Services, LDAP or similar ... In other projects, we managed the user authentication by creating tables that define all users and its allowed capacities, then the application queryies that data to verify if a user has access to some feature or not. ... The above ID and password are sent to the service at login time.... They are using Novell eDirectory at the enterprise level; yes it's LDAP.... We already do that for three different DB servers;... (borland.public.delphi.non-technical)
Re: noob on slapd with sasl errors ... If I may share advice based on my own trials & tribulations with LDAP... people who need network authentication and the current state of ... context of network authentication, LDAP really is just a protocol used ... I have no idea how sasl works and why it is needed here, or even more, ... (Ubuntu)
Re: Directory Services, LDAP or similar ... we managed the user authentication by creating tables ... The above ID and password are sent to the service at login... Novell eDirectory at the enterprise level; yes it's LDAP....servers;... (borland.public.delphi.non-technical)
Re: Recommended strategy for providing access to web apps via Inte ...LDAP is an ugly solution on the public internet,... These federated authentication protocols are designed to address these ... Co-author of "The .NET Developer's Guide to Directory Services Programming"... (microsoft.public.windows.server.active_directory)
Re: check a user password ... ADAM user you'll have perform an LDAP Bind operation,... However, as I said in another thread, LDAP is not an *authentication* protocol nor is "LDAP server" an authentication service. ... The LDAP bind operation is meant to "validate" the LDAP clients credentials in order, for the server, to be able to perform directory "authorization" checks. ... between a SQL client and a SQL server, or an authenticated session between a "Windows" client and a "File server" service. ... (microsoft.public.dotnet.languages.csharp)
