Back to bug 1015303
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Derek Horton | 2013-10-03 21:08:39 UTC | Link ID | JBoss Issue Tracker WFLY-2214 | |
| Petr Kremensky | 2013-10-04 06:46:27 UTC | QA Contact | pkremens | jcacek |
| Brian Stansberry | 2013-10-04 15:28:54 UTC | Assignee | brian.stansberry | darran.lofthouse |
| Brian Stansberry | 2013-10-04 15:29:43 UTC | CC | brian.stansberry | |
| Hisanobu Okuda | 2013-10-07 08:49:56 UTC | CC | hokuda | |
| Link ID | JBoss Issue Tracker PRODMGT-553 | |||
| Darran Lofthouse | 2013-11-20 13:19:36 UTC | Status | NEW | ASSIGNED |
| Darran Lofthouse | 2014-03-21 13:55:11 UTC | Status | ASSIGNED | POST |
| Darran Lofthouse | 2014-03-21 13:58:53 UTC | Doc Text | Cause: Outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behaviour. Consequence: It was not possible for custom properties to be defined to control thinks like connection and read timeouts. Fix: Custom properties can now be defined for the outbound LDAP connections e.g. <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> Result: Timeouts can now be specified using custom properties. |
|
| Kabir Khan | 2014-03-22 10:54:52 UTC | Status | POST | MODIFIED |
| Target Release | --- | EAP 6.3.0 | ||
| CC | kkhan | |||
| Target Milestone | --- | DR6 | ||
| Paul Gier | 2014-03-25 21:07:47 UTC | Status | MODIFIED | ON_QA |
| Ondrej Lukas | 2014-03-31 08:53:35 UTC | Status | ON_QA | VERIFIED |
| CC | olukas | |||
| Scott Mumford | 2014-04-28 04:44:57 UTC | CC | smumford | |
| Doc Text | Cause: Outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behaviour. Consequence: It was not possible for custom properties to be defined to control thinks like connection and read timeouts. Fix: Custom properties can now be defined for the outbound LDAP connections e.g. <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> Result: Timeouts can now be specified using custom properties. | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product, outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: <programlisting><![CDATA[<ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> ]]></programlisting> |
||
| Scott Mumford | 2014-05-13 00:13:41 UTC | CC | sgilda | |
| Doc Text | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product | ||
| Doc Text | , outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In | , outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In | ||
| Doc Text | this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: <programlisting><![CDATA[<ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly | this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly | ||
| Doc Text | ,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> ]]></programlisting> | ,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> | ||
| Doc Text | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product, outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product, outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: ---- <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> ---- |
||
| Scott Mumford | 2014-05-13 00:39:23 UTC | Doc Text | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product, outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: ---- <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> ---- | This release of JBoss EAP 6 contains an enhancement that allows the use of custom properties on outbound LDAP connections. In previous versions of the product, outbound LDAP connections were created with a limited set of properties leaving the remaining to the default behavior. As a result it was not possible for custom properties to be defined to control aspects such as connection and read timeouts. In this release, custom properties can now be defined for the outbound LDAP connections with code similar to the following: ---- <ldap name="LocalLdap" url="ldap://localhost:10389" search-dn="uid=wildfly,dc=simple,dc=wildfly,dc=org" search-credential="password1!"> <properties> <property name="one" value="two"/> <property name="three" value="four"/> </properties> </ldap> ---- |
| mark yarborough | 2014-06-28 15:44:45 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:44:45 UTC |
Back to bug 1015303