[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3946) LdapIdentityStore can not use backup server (failover)
by Raimund Hölle (JIRA)
LdapIdentityStore can not use backup server (failover)
------------------------------------------------------
Key: JBSEAM-3946
URL: https://jira.jboss.org/jira/browse/JBSEAM-3946
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1
Reporter: Raimund Hölle
Since LdapIdentityStore assembles the provider URL internally, it is not possible to use extended URL's, e. g., a primary and a backup server like this:
env.setProperty(Context.PROVIDER_URL, "ldap://srv01:389 ldap://srv02:389");
It would be nice if we would be able to set the providerUrl directly. For compatibility reasons, i suggest the following change:
// new property settable from components.xml
private String providerUrl = null;
protected final InitialLdapContext initialiseContext(String principal, String credentials) throws NamingException {
...
String url = providerUrl;
if (url == null || url.equals("")) {
url = String.format("ldap://%s:%d", getServerAddress(), getServerPort());
}
env.setProperty(Context.PROVIDER_URL, url);
...
Additionally it would be nice if initialiseContext() wouldn't be final so we are able to extend the class.
Regards,
Raimund
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2292) Resources from resource servlet can't be re-rendered
by Christian Bauer (JIRA)
Resources from resource servlet can't be re-rendered
----------------------------------------------------
Key: JBSEAM-2292
URL: http://jira.jboss.com/jira/browse/JBSEAM-2292
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Reporter: Christian Bauer
Found this after using the captcha:
<div class="input">
<a:region>
<s:validateAll>
<h:graphicImage value="/seam/resource/captcha" style="vertical-align:text-bottom;"/>
<h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}">
<a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/>
</h:inputText>
</s:validateAll>
</a:region>
</div>
This is a re-rendered s:decorate form field, so that onblur we get a new challenge (if the captcha repsonse was wrong). However, the graphicImage is not reloaded from the server, the browser caches it. To prevent browser caching, this is a quick hack:
<div class="input">
<a:region>
<s:validateAll>
<h:graphicImage value="/seam/resource/captcha?nocache=#{wiki:generateRandomNumber()}" style="vertical-align:text-bottom;"/>
<h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}">
<a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/>
</h:inputText>
</s:validateAll>
</a:region>
</div>
--
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
14 years, 8 months