Quoting Arnaud Blancher <[EMAIL PROTECTED]>:


<snip> Hi!

I am assuming that the inability to access Active Directory is a network issue,
right?

not really. the cluster is to heavy loaded (!!!) and he refuse new connection. clearly the AD don't work as is suppose to do ... but i cant change anything else in AD.

So, i would like to get the magic login of authenNTLM
(and the password if it possible) and do the autentification on another system
(not
define yet)


  Is there any way to deal with the problem on that front first?

If not, I see that we can add a PerlSetVar that will allow the module to send
DECLINED if the failure to the smb server fails.  (This would allow you to
chain authenhandlers to deal with this situation...)

yes, it ll be good. In this case, could i know the login (or does it need AD ?) </snip>

Hi!

I don't think that a modification to the module would be the best solution here.
It seems that the best solution is going to be at the directory services
cluster.


If we were to allow the AuthenNTLM module to DECLINE and use another alternative
authentication method, then you will need to mirror the AD passwords in some
other location... Is it possible to bring up a Backup Directory services
server outside of the cluster? You could then specify the backup as the
failover server, and authentication would always failover there, if the main
cluster was unreachable. If you can't have a backup server, then you would
need to choose another authentication scheme, (such as LDAP, NIS, etc.), the
problem being that it obviates the whole concept behind a directory service
anyways.


Sorry that I can't be of more help :(
--
Shannon Eric Peevey
President - EriKin Corporation
[EMAIL PROTECTED]
(940) 391-6777
http://www.erikin.com

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to