[
http://jira.jboss.com/jira/browse/JBAS-3553?page=all ]
Andy Brook updated JBAS-3553:
-----------------------------
Attachment: DCFailoverLDAPLoginModule.java
extension of LdapExtLoginModule that (I think) will, at initialisation, find a valid DC
and configure it appropriately if the primary or previous host is toast.
Failover 'java.naming.provider.url' entries
-------------------------------------------
Key: JBAS-3553
URL:
http://jira.jboss.com/jira/browse/JBAS-3553
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.4.GA
Environment: Linux, Debian (Ubuntu 6.0.6). LDAP server is M$ Active Directory
Reporter: Andy Brook
Assigned To: Scott M Stark
Attachments: DCFailoverLDAPLoginModule.java
We have a corporate net with multiple DC servers each acting as failovers for eachother.
I have to pick one as the naming provider in the LDAP LoginModules login-config.xml
section. A recent outage identified a weakness in this approach, the server was turned
off and all applicaitons went offline. I would like to suggest a bunch of alternate
naming providers that can be used if the main one goes offline.
I've just implemented this to address the problem but have yet to test it
extensively. Its not a complex fix, I just pull out <module-option
name="java.naming.provider.url.backups">abc|def</module-option> tags.
I check the availability of the given server at login module initialisation. I havent
figured out whether this is enough to work 'live' or require a server restart.
I'll attach what ive done for reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira