[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S edited comment on WFLY-7018 at 9/7/16 12:57 PM:
-------------------------------------------------------
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via {{<connection-property name="url">}} instead of {{<connection-url>}}, though I got exceptions unless both values where present (Like in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question 1:* It sounds like Wildfly DataSources will be configured differently in future, with different cli commands. Is this correct?
*Question 2:* Is there a better work-around than the above example, so that I can get a Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question 3:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration ({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ... --></subsystem>}}) that would work?
*Question 4:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration |http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
was (Author: marks1900):
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via {{<connection-property name="url">}} instead of {{<connection-url>}}, though I got exceptions unless both values where present (Like in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question 1:* In your recent comments, it sounds like Wildfly DataSources will be configured differently in future, with different cli commands. Is this correct?
*Question 2:* Is there a better work-around than the above example, so that I can get a Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question 3:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration ({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ... --></subsystem>}}) that would work?
*Question 4:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration |http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Lin Gao
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S edited comment on WFLY-7018 at 9/7/16 12:45 PM:
-------------------------------------------------------
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via {{<connection-property name="url">}} instead of {{<connection-url>}}, though I got exceptions unless both values where present (Like in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question 1:* In your recent comments, it sounds like Wildfly DataSources will be configured differently in future, with different cli commands. Is this correct?
*Question 2:* Is there a better work-around than the above example, so that I can get a Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question 3:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration ({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ... --></subsystem>}}) that would work?
*Question 4:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration |http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
was (Author: marks1900):
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via {{<connection-property name="url">}} instead of {{<connection-url>}}, though I got exceptions unless both values where present (Like in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question:* In your recent comments, it sounds like Wildfly DataSources will be configured differently in future, with different cli commands. Is this correct?
*Question:* Is there a better work-around than the above example, so that I can get a Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration ({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ... --></subsystem>}}) that would work?
*Question:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration |http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Lin Gao
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S commented on WFLY-7018:
------------------------------
Just a quick note. I set the {{datasource-class}} value (Which seems like it is the preferred way) and in Wildfly 10.1.0.Final I tried to set the connection value via {{<connection-property name="url">}} instead of {{<connection-url>}}, though I got exceptions unless both values where present (Like in the example above).
[~gaol]: I have a couple of questions in relation to your recent comments.
*Question:* In your recent comments, it sounds like Wildfly DataSources will be configured differently in future, with different cli commands. Is this correct?
*Question:* Is there a better work-around than the above example, so that I can get a Wildfly 10.0.0.Final DataSource working again in Wildfly 10.1.0.Final?
*Question:* Could you provide a sample Wildfly 10.1.0.Final DataSource XML configuration ({{<subsystem xmlns="urn:jboss:domain:datasources:4.0"><!-- ... --></subsystem>}}) that would work?
*Question:* Could you provide a sample Wildfly 10.1.0.Final DataSource CLI configuration that would work?
h3. Official Documentation on Wildfly 10 Datasources
[Official Wildfly 10 DataSource Configuration|https://docs.jboss.org/author/display/WFLY10/DataSource+con...]
Which links to [Official IronJacammar PostgresSql DataSource Configuration |http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html#ex_datasources_postgresql]
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Lin Gao
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1683) Home and End keys doesn't work on Windows
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1683?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky resolved WFCORE-1683.
---------------------------------------
Fix Version/s: 3.0.0.Alpha8
Resolution: Done
[~pkremens], thanks for confirming.
The bug has been fixed in Aesh 0.66.9. Current version used by the core is 0.66.10.
> Home and End keys doesn't work on Windows
> -----------------------------------------
>
> Key: WFCORE-1683
> URL: https://issues.jboss.org/browse/WFCORE-1683
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
> Fix For: 3.0.0.Alpha8
>
>
> Home and End keys doesn't work properly on Windows.
> *actual*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] echoαG[] test
> [disconnected /] echo<END> test
> [disconnected /] echoαO[] test
> {noformat}
> *expected*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] []echo test
> [disconnected /] echo<END> test
> [disconnected /] echo test[]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Lin Gao commented on WFLY-7018:
-------------------------------
When {{connection-url}} is defined, and the {{datasource-class}} is *NOT* defined either in {{driver}} or in {{data-source}} element, IronJacamar uses [java.sql.DriverManager.getConnection(String url, String username, String password)|https://docs.oracle.com/javase/8/docs/api/java/sql/DriverManage...] to get the database connection by using the specified {{connection-url}}.
When {{datasource-class}} is defined either in {{driver}} or in {{data-source}} element, IronJacamar uses DataSource to get the database connection, which is the [preferred way|https://docs.oracle.com/javase/tutorial/jdbc/basics/connecting.html].
A set of connection property needs to be defined to connect database via [DataSource|https://docs.oracle.com/javase/8/docs/api/javax/sql/DataSource...]. In case of PostgreSQL server, I think you can specify:
{code:xml}
<connection-property name="url">jdbc:postgresql://localhost:5432/myapp</connection-property>
{code}
instead of defining the {{<connection-url>}} in your configuration.
If you still want to use the {{connection-url}} configuration, remove the {{datasource-class}} definition in {{driver}} element can also be fine, but it is not recommended.
With WFCORE-1362 resolved, the command:
{code:java}
data-source add --connection-properties={"url"=>"myurl","user"=>"user","pass"=>"pass"}
{code}
supports specifying the {{connection-properties}} in one go when adding a new data-source.
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Lin Gao
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1683) Home and End keys doesn't work on Windows
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1683?page=com.atlassian.jira.plugi... ]
Petr Kremensky commented on WFCORE-1683:
----------------------------------------
[~aloubyansky] This one can be closed (not sure whether I can/should change the state of upstream issues thus letting you know)
> Home and End keys doesn't work on Windows
> -----------------------------------------
>
> Key: WFCORE-1683
> URL: https://issues.jboss.org/browse/WFCORE-1683
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Home and End keys doesn't work properly on Windows.
> *actual*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] echoαG[] test
> [disconnected /] echo<END> test
> [disconnected /] echoαO[] test
> {noformat}
> *expected*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] []echo test
> [disconnected /] echo<END> test
> [disconnected /] echo test[]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (SECURITY-955) Regression in parsing username in LdapExtLoginModule
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/SECURITY-955?page=com.atlassian.jira.plug... ]
Ilia Vassilev reassigned SECURITY-955:
--------------------------------------
Assignee: Ilia Vassilev (was: Stefan Guilhen)
> Regression in parsing username in LdapExtLoginModule
> ----------------------------------------------------
>
> Key: SECURITY-955
> URL: https://issues.jboss.org/browse/SECURITY-955
> Project: PicketBox
> Issue Type: Bug
> Affects Versions: PicketBox_5_0_0.Alpha3
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
> Priority: Blocker
>
> In case when customers using LdapExtLoginModule with option parseUsername=true but without option usernameBeginString (i.e. usernameBeginString=null) then all users cannot be successfully authenticated into application. Authentication failure is caused by hidden internal NPE.
> It is the same issue as was reported in [1], but fix is missing in current EAP 7.1 version of PicketBox (5.0.0.Alpha3).
> We request blocker flag because:
> * Valid configuration which works for 7.0.x becomes invalid after migration to 7.1.0
> * All users cannot authenticate to application despite of valid EAP configuration
> * Authetication failure caused by NPE is logged to server log
> Thrown NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.security.auth.spi.LdapExtLoginModule.getUsername(LdapExtLoginModule.java:963)
> at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:342)
> at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283)
> {code}
> [1] https://issues.jboss.org/browse/JBEAP-364?focusedCommentId=13160168&page=...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (SECURITY-956) New behavior for empty string in rolesCtxDN in LdapExtLoginModule in EAP 7.1
by Ondrej Lukas (JIRA)
Ondrej Lukas created SECURITY-956:
-------------------------------------
Summary: New behavior for empty string in rolesCtxDN in LdapExtLoginModule in EAP 7.1
Key: SECURITY-956
URL: https://issues.jboss.org/browse/SECURITY-956
Project: PicketBox
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Stefan Guilhen
In case when LdapExtLoginModule has option rolesCtxDN set to empty string then it has different behavior in EAP 7.0 (PicketBox 4.9.x) and 7.1 (PicketBox 5.0.x).
EAP 7.0 uses empty string as base search for LDAP.
* In case when LDAP server supports empty string search base (e.g. Apache DS allows it) it works as expected, all LDAP tree is searched for roles.
* In case when LDAP server does not support empty string search base (e.g. Active Directory or Red Hat Directory Server) it thrown exception authentication fails. However exception is expected since it is misconfiguration for those LDAP servers.
EAP 7.1 does not search any roles for empty string. That means:
* In case when LDAP server supports empty string search base it does not find any roles. However some roles could be found on that type of LDAP servers.
* In case when LDAP server does not support empty string search base it correctly returns no roles and authentication passes.
>From my PoV, behavior from EAP 7.0 is more correct, because it works correctly for LDAP servers where empty string is legal search base. However it can be decided that current EAP 7.1 behavior is intended. In that case please create Release Notes Jira (because it is change in behavior) and close this Jira.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months