]
Martin Choma moved JBEAP-7611 to WFLY-7720:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7720 (was: JBEAP-7611)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR9)
Expose generic options for elytron dir-context
----------------------------------------------
Key: WFLY-7720
URL:
https://issues.jboss.org/browse/WFLY-7720
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Priority: Critical
Expose generic options like in case of legacy ldap outbound connection. Users relying on
them can't migrate to elytron.
As [~tfonteyn] has already [pointed
out|https://issues.jboss.org/browse/JBEAP-6480?focusedCommentId=13312043&...]
customers use generic options exposed by legacy ldap outbound connection.
Here are references to possible properties to be configured
* [list of general
properties|http://docs.oracle.com/javase/jndi/tutorial/beyond/env/overvie...]
** Service-specific
*** e.g. java.naming.ldap.* , for example for [connection pool
configuration|http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/co...]
** Feature-specific
*** e.g.
[
java.naming.security.sasl.*|http://docs.oracle.com/javase/jndi/tutorial/l...]
** Provider-specific
*** e.g. com.sun.jndi.ldap.trace.ber
AFAICT it is already prepared in elytron, just elytron-subsystem part is missing.
{code:title=SimpleDirContextFactoryBuilder.java}
// set any additional connection property
if (connectionProperties != null) {
for (Object key : connectionProperties.keySet()) {
Object value = connectionProperties.get(key.toString());
if (value != null) {
env.put(key.toString(), value.toString());
}
}
}
{code}