[jboss-jira] [JBoss JIRA] (WFLY-7720) Expose generic options for elytron dir-context

[Martin Choma (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Choma updated WFLY-7720:
-------------------------------
    Description: 
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&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13312043] customers use generic options exposed by legacy ldap outbound connection.

Here are references to possible properties to be configured
* [general properties|http://docs.oracle.com/javase/jndi/tutorial/beyond/env/overview.html]
* Service-specific
** e.g. java.naming.ldap.* , for example for [connection pool configuration|http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html] 
* Feature-specific
** e.g. [java.naming.security.sasl.*|http://docs.oracle.com/javase/jndi/tutorial/ldap/security/sasl.html] 
* 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}


  was:
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&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-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/overview.html]
** Service-specific
*** e.g. java.naming.ldap.* , for example for [connection pool configuration|http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html] 
** Feature-specific
*** e.g. [java.naming.security.sasl.*|http://docs.oracle.com/javase/jndi/tutorial/ldap/security/sasl.html] 
** 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}




> 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&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13312043] customers use generic options exposed by legacy ldap outbound connection.
> Here are references to possible properties to be configured
> * [general properties|http://docs.oracle.com/javase/jndi/tutorial/beyond/env/overview.html]
> * Service-specific
> ** e.g. java.naming.ldap.* , for example for [connection pool configuration|http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html] 
> * Feature-specific
> ** e.g. [java.naming.security.sasl.*|http://docs.oracle.com/javase/jndi/tutorial/ldap/security/sasl.html] 
> * 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}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)