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
  • e.g. java.naming.security.sasl.*
• Provider-specific
  • e.g. com.sun.jndi.ldap.trace.ber

AFAICT it is already prepared in elytron, just elytron-subsystem part is missing.

            // 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());
                    }
                }
            }