-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR9
-
None
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 customers use generic options exposed by legacy ldap outbound connection.
Here are references to possible properties to be configured
- General properties
- Service-specific
- e.g. java.naming.ldap.* , for example for connection pool configuration
- Feature-specific
- Provider-specific
- e.g. com.sun.jndi.ldap.trace.ber
AFAICT it is already prepared in elytron, just elytron-subsystem part is missing.
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()); } } }
- is cloned by
-
WFLY-7720 Expose generic options for elytron dir-context
- Closed
- is incorporated by
-
JBEAP-8259 Upgrade to Elytron Subsystem 1.0.0.Alpha20
- Closed
- is related to
-
JBEAP-8025 Initial context factory is not able to be set in Elytron dir-context
- Closed