[jira] [Updated] (FC-230) Support Java 11+
[ https://issues.apache.org/jira/browse/FC-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-230: -- Summary: Support Java 11+ (was: Support Java 9) > Support Java 11+ > > > Key: FC-230 > URL: https://issues.apache.org/jira/browse/FC-230 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > > Add Java 9 support. Upgrade version mvn plugins: > 1. maven-jar-plugin > 3.0.2 > 2. maven-source-plugin > 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-230) Support Java 11+
[
https://issues.apache.org/jira/browse/FC-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-230:
--
Description:
Add Java 11 support. Upgrade version mvn plugins:
org.apache.maven.plugins
maven-compiler-plugin
3.8.0
${java.version}
${java.version}
true
ISO-8859-1
was:
Add Java 9 support. Upgrade version mvn plugins:
1. maven-jar-plugin
3.0.2
2. maven-source-plugin
3.0.0
> Support Java 11+
>
>
> Key: FC-230
> URL: https://issues.apache.org/jira/browse/FC-230
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
>
> Add Java 11 support. Upgrade version mvn plugins:
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.8.0
>
> ${java.version}
> ${java.version}
> true
> ISO-8859-1
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (FC-272) Batch size limit
[ https://issues.apache.org/jira/browse/FC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-272: - Assignee: Shawn McKinney > Batch size limit > > > Key: FC-272 > URL: https://issues.apache.org/jira/browse/FC-272 > Project: FORTRESS > Issue Type: New Feature >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > > The batch file limit is a constant definied in code and it should be possible > in the request define a new batch size limit. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (FC-273) Object Pagination
[ https://issues.apache.org/jira/browse/FC-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-273: - Assignee: Shawn McKinney > Object Pagination > - > > Key: FC-273 > URL: https://issues.apache.org/jira/browse/FC-273 > Project: FORTRESS > Issue Type: New Feature >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > > It should be possible, when the number of objects in LDAP is over the Bacth > size limit, to use pagination to retrive all the objects. > (This was observed in REST interface) -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-272) Batch size limit
[ https://issues.apache.org/jira/browse/FC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-272: -- Fix Version/s: 2.0.4 > Batch size limit > > > Key: FC-272 > URL: https://issues.apache.org/jira/browse/FC-272 > Project: FORTRESS > Issue Type: New Feature >Affects Versions: 2.0.3 >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.4 > > > The batch file limit is a constant definied in code and it should be possible > in the request define a new batch size limit. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-272) Batch size limit
[ https://issues.apache.org/jira/browse/FC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-272: -- Affects Version/s: 2.0.3 > Batch size limit > > > Key: FC-272 > URL: https://issues.apache.org/jira/browse/FC-272 > Project: FORTRESS > Issue Type: New Feature >Affects Versions: 2.0.3 >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > > The batch file limit is a constant definied in code and it should be possible > in the request define a new batch size limit. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-272) Batch size limit
[ https://issues.apache.org/jira/browse/FC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895520#comment-16895520 ] Shawn McKinney commented on FC-272: --- The behavior will be that 1000 will continue to be the default batch size. A user can override by placing a property in the build.property / slapd.property file: This sets the maximum search result set from LDAP, default is 1000: ldap.max.batch.size=2000 Which will then get set in the fortress configuration node stored in LDAP. As always, the user can always just place the configuration entry into the fortress.property file itself. Add property to fortress.property or LDAP config node: ldap.search.max.batch.size:2000 > Batch size limit > > > Key: FC-272 > URL: https://issues.apache.org/jira/browse/FC-272 > Project: FORTRESS > Issue Type: New Feature >Affects Versions: 2.0.3 >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.4 > > > The batch file limit is a constant definied in code and it should be possible > in the request define a new batch size limit. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-274) Upgrade maven plugins and dependencies
Shawn McKinney created FC-274: - Summary: Upgrade maven plugins and dependencies Key: FC-274 URL: https://issues.apache.org/jira/browse/FC-274 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.3 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 2.0.4 Exclude dom4j from ldap api due to CVE-2018-1000632. Note, this has been upgraded to proper version in latest api, but fortress is on back level 1.x 2.1.1 More changes to depends: fortress core: [INFO] The following dependencies in Dependencies have newer versions: [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 * [INFO] commons-codec:commons-codec . 1.11 -> 1.13 * [INFO] javax:javaee-api 8.0 -> 8.0.1 * [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 * [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 * [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 * [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 * [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 * [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 * (1.7.29) [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 * (1.7.29) also updated plugs for core: [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 [INFO] maven-site-plugin .. 3.4 -> 3.8.2 [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 except for: [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-274) Upgrade maven plugins and dependencies
[ https://issues.apache.org/jira/browse/FC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992763#comment-16992763 ] Shawn McKinney commented on FC-274: --- More changes to core depends: To: com.sun.xml.bind jaxb-impl 2.3.2 test org.glassfish.jaxb jaxb-core 2.3.0.1 test > Upgrade maven plugins and dependencies > --- > > Key: FC-274 > URL: https://issues.apache.org/jira/browse/FC-274 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Exclude dom4j from ldap api due to CVE-2018-1000632. > > Note, this has been upgraded to proper version in latest api, but fortress is > on back level 1.x > > 2.1.1 > > More changes to depends: > fortress core: > [INFO] The following dependencies in Dependencies have newer versions: > [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 > * > [INFO] commons-codec:commons-codec . 1.11 -> 1.13 > * > [INFO] javax:javaee-api 8.0 -> 8.0.1 > * > [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 > * > [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 > * > [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 > * > [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 > * > [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 > * > [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > > also updated plugs for core: > > [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 > [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 > [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 > [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 > [INFO] maven-site-plugin .. 3.4 -> 3.8.2 > [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 > [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 > > except for: > [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 > > which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-274) Upgrade maven plugins and dependencies
[ https://issues.apache.org/jira/browse/FC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992832#comment-16992832 ] Shawn McKinney commented on FC-274: --- Updates to the Realm: realm: [INFO] --- versions-maven-plugin:2.2:display-dependency-updates (default-cli) @ fortress-realm-proxy --- [INFO] The following dependencies in Dependency Management have newer versions: [INFO] org.apache.tomcat:tomcat-catalina ... 7.0.92 -> 9.0.29 [INFO] [INFO] The Building Apache Fortress Realm Implementation 2.0.4-SNAPSHOT [3/3] [INFO] [ jar ]- [INFO] [INFO] --- versions-maven-plugin:2.2:display-plugin-updates (default-cli) @ fortress-realm-impl --- [INFO] [INFO] The following plugin updates are available: [INFO] maven-jar-plugin ... 2.5 -> 3.2.0 [INFO] > Upgrade maven plugins and dependencies > --- > > Key: FC-274 > URL: https://issues.apache.org/jira/browse/FC-274 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Exclude dom4j from ldap api due to CVE-2018-1000632. > > Note, this has been upgraded to proper version in latest api, but fortress is > on back level 1.x > > 2.1.1 > > More changes to depends: > fortress core: > [INFO] The following dependencies in Dependencies have newer versions: > [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 > * > [INFO] commons-codec:commons-codec . 1.11 -> 1.13 > * > [INFO] javax:javaee-api 8.0 -> 8.0.1 > * > [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 > * > [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 > * > [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 > * > [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 > * > [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 > * > [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > > also updated plugs for core: > > [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 > [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 > [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 > [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 > [INFO] maven-site-plugin .. 3.4 -> 3.8.2 > [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 > [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 > > except for: > [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 > > which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-274) Upgrade maven plugins and dependencies
[ https://issues.apache.org/jira/browse/FC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992977#comment-16992977 ] Shawn McKinney commented on FC-274: --- enmasse: plugins: [INFO] The following plugin updates are available: [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 [INFO] maven-war-plugin ... 2.4 -> 3.2.3 dependencies: The following dependencies in Dependencies have newer versions: [INFO] com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider ... [INFO] 2.9.7 -> 2.10.1 [INFO] com.sun.xml.bind:jaxb-core .. 2.3.0 -> org.glassfish.jaxb 2.3.0.1 [INFO] com.sun.xml.bind:jaxb-impl 2.3.0 -> 2.3.2 [INFO] org.apache.cxf:cxf-core ... 3.2.6 -> 3.3.4 [INFO] org.apache.cxf:cxf-rt-frontend-jaxrs .. 3.2.6 -> 3.3.4 [INFO] org.springframework:spring-core ... 5.0.9.RELEASE -> 5.2.2.RELEASE [INFO] org.springframework.security:spring-security-web ... [INFO] 5.0.7.RELEASE -> 5.2.1.RELEASE > Upgrade maven plugins and dependencies > --- > > Key: FC-274 > URL: https://issues.apache.org/jira/browse/FC-274 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Exclude dom4j from ldap api due to CVE-2018-1000632. > > Note, this has been upgraded to proper version in latest api, but fortress is > on back level 1.x > > 2.1.1 > > More changes to depends: > fortress core: > [INFO] The following dependencies in Dependencies have newer versions: > [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 > * > [INFO] commons-codec:commons-codec . 1.11 -> 1.13 > * > [INFO] javax:javaee-api 8.0 -> 8.0.1 > * > [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 > * > [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 > * > [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 > * > [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 > * > [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 > * > [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > > also updated plugs for core: > > [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 > [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 > [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 > [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 > [INFO] maven-site-plugin .. 3.4 -> 3.8.2 > [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 > [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 > > except for: > [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 > > which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-274) Upgrade maven plugins and dependencies
[ https://issues.apache.org/jira/browse/FC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992986#comment-16992986 ] Shawn McKinney commented on FC-274: --- commander: [INFO] The following plugin updates are available: [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 [INFO] maven-war-plugin ... 2.4 -> 3.2.3 [INFO] org.codehaus.mojo:tomcat-maven-plugin . 1.0-beta-1 -> 1.1 > Upgrade maven plugins and dependencies > --- > > Key: FC-274 > URL: https://issues.apache.org/jira/browse/FC-274 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Exclude dom4j from ldap api due to CVE-2018-1000632. > > Note, this has been upgraded to proper version in latest api, but fortress is > on back level 1.x > > 2.1.1 > > More changes to depends: > fortress core: > [INFO] The following dependencies in Dependencies have newer versions: > [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 > * > [INFO] commons-codec:commons-codec . 1.11 -> 1.13 > * > [INFO] javax:javaee-api 8.0 -> 8.0.1 > * > [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 > * > [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 > * > [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 > * > [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 > * > [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 > * > [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > > also updated plugs for core: > > [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 > [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 > [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 > [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 > [INFO] maven-site-plugin .. 3.4 -> 3.8.2 > [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 > [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 > > except for: > [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 > > which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-275) some java doc cleanup
Shawn McKinney created FC-275: - Summary: some java doc cleanup Key: FC-275 URL: https://issues.apache.org/jira/browse/FC-275 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.3 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 2.0.4 Get some longstanding problems cleaned up. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-238) Migrate to LDAP API 2.0
[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-238: -- Fix Version/s: (was: 2.0.4) 3.0.0-RC1 > Migrate to LDAP API 2.0 > --- > > Key: FC-238 > URL: https://issues.apache.org/jira/browse/FC-238 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: Shawn McKinney >Assignee: Emmanuel Lécharny >Priority: Major > Fix For: 3.0.0-RC1 > > > The code compiles, but gets NPE when fortress tries to open a pool to the > server > ** > Steps to recreate. > # Get fortress env, checkout latest, follow the steps in DOCKER README to > get either openldap or apacheds server up. > # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file= > ## in order to verify the env is running correctly run this test: > ### mvn test -Pconsole <-– should be no errors > # Now checkout the code that is using ldap api 2.0.0 > ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000 > # connect with fortress console: > ## mvn test -Pconsole > Get the error: > > 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 - > MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4) > [WARNING] > org.apache.directory.fortress.core.CfgRuntimeException: Exception caught > initializing Admin Pool: java.lang.NullPointerException, errCode=135 > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103) > at > org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215) > at > org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327) > at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175) > at > org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102) > at > org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377) > at > org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655) > at > org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101) > at > org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68) > at > org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74) > at > org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38) > at > org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313) > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180) > ... 19 more > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-247) Create a New Webapp to Manage Fortress Entities
[ https://issues.apache.org/jira/browse/FC-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-247: -- Fix Version/s: (was: 2.0.4) 3.0.0-RC1 > Create a New Webapp to Manage Fortress Entities > --- > > Key: FC-247 > URL: https://issues.apache.org/jira/browse/FC-247 > Project: FORTRESS > Issue Type: Task >Reporter: Kiran Ayyagari >Assignee: Kiran Ayyagari >Priority: Major > Fix For: 3.0.0-RC1 > > > Fortress has a Apache Wicket based webapp that is used for managing various > entities. > There is a new plan to re-write it using [Vue.JS|https://vuejs.org/].This > task is intended for > tracking the progress of this new experiment. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-274) Upgrade maven plugins and dependencies
[ https://issues.apache.org/jira/browse/FC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-274. --- Resolution: Fixed > Upgrade maven plugins and dependencies > --- > > Key: FC-274 > URL: https://issues.apache.org/jira/browse/FC-274 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Exclude dom4j from ldap api due to CVE-2018-1000632. > > Note, this has been upgraded to proper version in latest api, but fortress is > on back level 1.x > > 2.1.1 > > More changes to depends: > fortress core: > [INFO] The following dependencies in Dependencies have newer versions: > [INFO] com.fasterxml.jackson.core:jackson-annotations ... 2.9.7 -> 2.10.1 > * > [INFO] commons-codec:commons-codec . 1.11 -> 1.13 > * > [INFO] javax:javaee-api 8.0 -> 8.0.1 > * > [INFO] javax.ws.rs:javax.ws.rs-api . 2.1 -> 2.1.1 > * > [INFO] org.apache.httpcomponents:httpclient . 4.5.6 -> 4.5.10 > * > [INFO] org.apache.httpcomponents:httpcore .. 4.4.10 -> 4.4.12 > * > [INFO] org.jasypt:jasypt . 1.9.2 -> 1.9.3 > * > [INFO] org.jgrapht:jgrapht-core .. 1.0.0 -> 1.3.1 > * > [INFO] org.slf4j:slf4j-api ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > [INFO] org.slf4j:slf4j-log4j12 ... 1.7.21 -> 2.0.0-alpha1 > * (1.7.29) > > also updated plugs for core: > > [INFO] maven-assembly-plugin 3.0.0 -> 3.2.0 > [INFO] maven-clean-plugin ... 3.0.0 -> 3.1.0 > [INFO] maven-compiler-plugin 3.8.0 -> 3.8.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-install-plugin 2.5.2 -> 3.0.0-M1 > [INFO] maven-jar-plugin . 3.0.2 -> 3.2.0 > [INFO] maven-site-plugin .. 3.4 -> 3.8.2 > [INFO] maven-source-plugin .. 3.0.0 -> 3.2.0 > [INFO] org.owasp:dependency-check-maven . 3.3.4 -> 5.0.0 > > except for: > [INFO] maven-surefire-plugin 2.18.1 -> 3.0.0-M4 > > which causes the test behavior to change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-275) some java doc cleanup
[ https://issues.apache.org/jira/browse/FC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-275. --- Resolution: Fixed > some java doc cleanup > - > > Key: FC-275 > URL: https://issues.apache.org/jira/browse/FC-275 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Get some longstanding problems cleaned up. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-272) Batch size limit
[ https://issues.apache.org/jira/browse/FC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-272. --- Resolution: Fixed > Batch size limit > > > Key: FC-272 > URL: https://issues.apache.org/jira/browse/FC-272 > Project: FORTRESS > Issue Type: New Feature >Affects Versions: 2.0.3 >Reporter: Nuno Miquelina >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.4 > > > The batch file limit is a constant definied in code and it should be possible > in the request define a new batch size limit. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-265) Delegated Administration Enhancements to Apache Fortress REST
[ https://issues.apache.org/jira/browse/FC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993702#comment-16993702 ] Shawn McKinney commented on FC-265: --- Also described here: https://github.com/apache/directory-fortress-enmasse/blob/master/README-SECURITY-MODEL.md > Delegated Administration Enhancements to Apache Fortress REST > - > > Key: FC-265 > URL: https://issues.apache.org/jira/browse/FC-265 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > Described here: > http://mail-archives.apache.org/mod_mbox/directory-fortress/201903.mbox/%3c77dc86d5-8ca5-4089-8f1a-5c373752e...@apache.org%3e -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-276) Correct ant config processing of conditionals like enable ssl or rbac accelerator
Shawn McKinney created FC-276: - Summary: Correct ant config processing of conditionals like enable ssl or rbac accelerator Key: FC-276 URL: https://issues.apache.org/jira/browse/FC-276 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 This problem came up working on rbac accelerator enablement / disablement. The conditional: This target would execute if this variable was set in the .properties file: rbac.accelerator=anything Correct to only fire when condition is true: rbac.accelerator=true Also made same change for enable.ssl -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-276) Correct ant config processing of conditionals like enable ssl or rbac accelerator
[
https://issues.apache.org/jira/browse/FC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041250#comment-17041250
]
Shawn McKinney commented on FC-276:
---
For further details on conditional ant syntax:
https://ant.apache.org/manual/properties.html#if+unless
> Correct ant config processing of conditionals like enable ssl or rbac
> accelerator
> -
>
> Key: FC-276
> URL: https://issues.apache.org/jira/browse/FC-276
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> This problem came up working on rbac accelerator enablement / disablement.
> The conditional:
>
>
>
> This target would execute if this variable was set in the .properties file:
> rbac.accelerator=anything
>
> Correct to only fire when condition is true:
> if="${rbac.accelerator}">
> rbac.accelerator=true
>
> Also made same change for enable.ssl
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-277) Clean up the RBAC accelerator enablement
Shawn McKinney created FC-277: - Summary: Clean up the RBAC accelerator enablement Key: FC-277 URL: https://issues.apache.org/jira/browse/FC-277 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Recent changes over the last couple of years removed an ACL that was needed for the RBAC accelerator overlay to access the default DB, using a root dn from a separate database. Change the default config for the accelerator to use the same root dn as the default database negating the need for a separate ACL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-278) RestUtils throws NPE when trust.store property null for non-TLS conns
Shawn McKinney created FC-278: - Summary: RestUtils throws NPE when trust.store property null for non-TLS conns Key: FC-278 URL: https://issues.apache.org/jira/browse/FC-278 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Never throw an NPE but this property should only need to be set when using HTTPS with the host. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-278) RestUtils throws NPE when trust.store property null for non-TLS conns
[
https://issues.apache.org/jira/browse/FC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-278.
---
Resolution: Fixed
enclosed in a null check:
if( StringUtils.isNotEmpty(trustStore ) && StringUtils.isNotEmpty(trustStorePw
) )
{
LOG.info( "javax.net.ssl.trustStore: {}", trustStore );
System.setProperty( "javax.net.ssl.trustStore", trustStore );
System.setProperty( "javax.net.ssl.trustStorePassword", trustStorePw );
}
> RestUtils throws NPE when trust.store property null for non-TLS conns
> -
>
> Key: FC-278
> URL: https://issues.apache.org/jira/browse/FC-278
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> Never throw an NPE but this property should only need to be set when using
> HTTPS with the host.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-279) RestUtils error mapping for HTTP 404 error
Shawn McKinney created FC-279: - Summary: RestUtils error mapping for HTTP 404 error Key: FC-279 URL: https://issues.apache.org/jira/browse/FC-279 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404 error gets masked, as the response is attempted to be parsed. Fix the error handing to properly catch 404 error and map to appropriate exception. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-279) Fix RestUtils error mapping for HTTP errors
[ https://issues.apache.org/jira/browse/FC-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-279: -- Summary: Fix RestUtils error mapping for HTTP errors (was: RestUtils error mapping for HTTP 404 error) > Fix RestUtils error mapping for HTTP errors > --- > > Key: FC-279 > URL: https://issues.apache.org/jira/browse/FC-279 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404 > error gets masked, as the response is attempted to be parsed. > > Fix the error handing to properly catch 404 error and map to appropriate > exception. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-279) Fix RestUtils error mapping for HTTP errors
[
https://issues.apache.org/jira/browse/FC-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-279:
--
Description:
The problem:
Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404
error gets masked, as the response is attempted to be parsed.
Fix the error handing to properly catch http errors and map to appropriate
exception.
There's a bit more to this. That is currently Fortress Rest maps application
defined errors, e.g. read and authentication failures to HTTP error codes, in
addition to the application status codes.
The rationale, so certain RESTful clients, i.e. the new Fortress UI don't have
to crack the message when errors happen.
Impedance mismatch between generic HTTP errors and application defined errors
notwithstanding, there needs to be a way to differentiate between generic HTTP
errors, i.e. thrown by Tomcat, and application defined HTTP errors, thrown by
the Fortress Rest processor.
***
The solution, is to examine the response, in addition to the error code, to
determine if generic HTTP errors should be thrown, or if normal processing
should resume.
{{ case HTTP_404_NOT_FOUND:}}
{{ szResponse = IOUtils.toString( response.getEntity().getContent(), "UTF-8"
);}}
{{ // Crack the response and see if it can be parsed as a valid Fortress
Response object or generic HTTP:}}
{{ if( StringUtils.isNotEmpty( szResponse ) &&
szResponse.contains(VALID_RESPONSE) )}}
{{ {}}
{{ LOG.debug( "HTTP: 404: post uri=[{}], function=[{}], response=[{}]", uri,
function, szResponse );}}
{{ }}}
{{ else}}
{{ {}}
{{ error = generateErrorMessage( uri, function, "HTTP Error:" +
response.getStatusLine().getStatusCode());}}
{{ LOG.error( error );}}
{{ throw new RestException( GlobalErrIds.REST_NOT_FOUND_ERR, error );}}
{{ }}}
{{ break;}}
was:
Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404
error gets masked, as the response is attempted to be parsed.
Fix the error handing to properly catch 404 error and map to appropriate
exception.
> Fix RestUtils error mapping for HTTP errors
> ---
>
> Key: FC-279
> URL: https://issues.apache.org/jira/browse/FC-279
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> The problem:
> Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404
> error gets masked, as the response is attempted to be parsed.
> Fix the error handing to properly catch http errors and map to appropriate
> exception.
> There's a bit more to this. That is currently Fortress Rest maps application
> defined errors, e.g. read and authentication failures to HTTP error codes, in
> addition to the application status codes.
> The rationale, so certain RESTful clients, i.e. the new Fortress UI don't
> have to crack the message when errors happen.
> Impedance mismatch between generic HTTP errors and application defined errors
> notwithstanding, there needs to be a way to differentiate between generic
> HTTP errors, i.e. thrown by Tomcat, and application defined HTTP errors,
> thrown by the Fortress Rest processor.
> ***
> The solution, is to examine the response, in addition to the error code, to
> determine if generic HTTP errors should be thrown, or if normal processing
> should resume.
> {{ case HTTP_404_NOT_FOUND:}}
> {{ szResponse = IOUtils.toString( response.getEntity().getContent(), "UTF-8"
> );}}
> {{ // Crack the response and see if it can be parsed as a valid Fortress
> Response object or generic HTTP:}}
> {{ if( StringUtils.isNotEmpty( szResponse ) &&
> szResponse.contains(VALID_RESPONSE) )}}
> {{ {}}
> {{ LOG.debug( "HTTP: 404: post uri=[{}], function=[{}], response=[{}]",
> uri, function, szResponse );}}
> {{ }}}
> {{ else}}
> {{ {}}
> {{ error = generateErrorMessage( uri, function, "HTTP Error:" +
> response.getStatusLine().getStatusCode());}}
> {{ LOG.error( error );}}
> {{ throw new RestException( GlobalErrIds.REST_NOT_FOUND_ERR, error );}}
> {{ }}}
> {{ break;}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-280) Verify role constraint exists before assigning to a user
Shawn McKinney created FC-280: - Summary: Verify role constraint exists before assigning to a user Key: FC-280 URL: https://issues.apache.org/jira/browse/FC-280 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Should prevent user-role constraints from being added if the role constraint doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (FC-230) Support Java 11+
[
https://issues.apache.org/jira/browse/FC-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney closed FC-230.
-
Resolution: Fixed
> Support Java 11+
>
>
> Key: FC-230
> URL: https://issues.apache.org/jira/browse/FC-230
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
>
> Add Java 11 support. Upgrade version mvn plugins:
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.8.0
>
> ${java.version}
> ${java.version}
> true
> ISO-8859-1
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-271) 3.0.0 Roadmap
[ https://issues.apache.org/jira/browse/FC-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-271: -- Description: Currently under consideration: # Combining the four git repos into one. # Upgrade to LDAP API 2.0 # Persistent searches replace ehcache in Core. # Support paging in Core API and Rest services. # Break the Core into separate modules. was: Currently under consideration: # Combining the four git repos into one. # Upgrade to LDAP API 2.0 # Persistent searches replace ehcache > 3.0.0 Roadmap > - > > Key: FC-271 > URL: https://issues.apache.org/jira/browse/FC-271 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > Currently under consideration: > # Combining the four git repos into one. > # Upgrade to LDAP API 2.0 > # Persistent searches replace ehcache in Core. > # Support paging in Core API and Rest services. > # Break the Core into separate modules. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-281) [FORTRESS-WEB] Upgrade to Wicket version 8
Shawn McKinney created FC-281: - Summary: [FORTRESS-WEB] Upgrade to Wicket version 8 Key: FC-281 URL: https://issues.apache.org/jira/browse/FC-281 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Bump up to Wicket 8. This requires a change on nearly every page, to change the way callbacks for Ajax buttons and links. Also bump up to latest Spring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-281) [FORTRESS-WEB] Upgrade to Wicket version 8
[ https://issues.apache.org/jira/browse/FC-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106567#comment-17106567 ] Shawn McKinney commented on FC-281: --- Use latest stable release of the following: org.apache.wicket wicket-spring 8.8.0 org.wicketstuff wicketstuff-inmethod-grid 8.8.0 com.googlecode.wicket-jquery-ui wicket-jquery-ui 8.6.0 com.googlecode.wicket-jquery-ui wicket-kendo-ui 8.6.0 org.springframework.security spring-security-config 5.3.2.RELEASE org.springframework.security spring-security-web 5.3.2.RELEASE > [FORTRESS-WEB] Upgrade to Wicket version 8 > -- > > Key: FC-281 > URL: https://issues.apache.org/jira/browse/FC-281 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > Bump up to Wicket 8. This requires a change on nearly every page, to change > the way callbacks for Ajax buttons and links. > > Also bump up to latest Spring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-281) [FORTRESS-WEB] Upgrade to Wicket version 8
[ https://issues.apache.org/jira/browse/FC-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-281. --- Resolution: Fixed > [FORTRESS-WEB] Upgrade to Wicket version 8 > -- > > Key: FC-281 > URL: https://issues.apache.org/jira/browse/FC-281 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > Bump up to Wicket 8. This requires a change on nearly every page, to change > the way callbacks for Ajax buttons and links. > > Also bump up to latest Spring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-278) RestUtils throws NPE when trust.store property null for non-TLS conns
[ https://issues.apache.org/jira/browse/FC-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-278: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.5 > RestUtils throws NPE when trust.store property null for non-TLS conns > - > > Key: FC-278 > URL: https://issues.apache.org/jira/browse/FC-278 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Never throw an NPE but this property should only need to be set when using > HTTPS with the host. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-277) Clean up the RBAC accelerator enablement
[ https://issues.apache.org/jira/browse/FC-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-277. --- Resolution: Fixed > Clean up the RBAC accelerator enablement > > > Key: FC-277 > URL: https://issues.apache.org/jira/browse/FC-277 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Recent changes over the last couple of years removed an ACL that was needed > for the RBAC accelerator overlay to access the default DB, using a root dn > from a separate database. > > Change the default config for the accelerator to use the same root dn as the > default database negating the need for a separate ACL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-277) Clean up the RBAC accelerator enablement
[ https://issues.apache.org/jira/browse/FC-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-277: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.5 > Clean up the RBAC accelerator enablement > > > Key: FC-277 > URL: https://issues.apache.org/jira/browse/FC-277 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Recent changes over the last couple of years removed an ACL that was needed > for the RBAC accelerator overlay to access the default DB, using a root dn > from a separate database. > > Change the default config for the accelerator to use the same root dn as the > default database negating the need for a separate ACL. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-280) Verify role constraint exists before assigning to a user
[ https://issues.apache.org/jira/browse/FC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-280: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.5 > Verify role constraint exists before assigning to a user > > > Key: FC-280 > URL: https://issues.apache.org/jira/browse/FC-280 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Should prevent user-role constraints from being added if the role constraint > doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-279) Fix RestUtils error mapping for HTTP errors
[
https://issues.apache.org/jira/browse/FC-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-279.
---
Resolution: Fixed
> Fix RestUtils error mapping for HTTP errors
> ---
>
> Key: FC-279
> URL: https://issues.apache.org/jira/browse/FC-279
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> The problem:
> Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404
> error gets masked, as the response is attempted to be parsed.
> Fix the error handing to properly catch http errors and map to appropriate
> exception.
> There's a bit more to this. That is currently Fortress Rest maps application
> defined errors, e.g. read and authentication failures to HTTP error codes, in
> addition to the application status codes.
> The rationale, so certain RESTful clients, i.e. the new Fortress UI don't
> have to crack the message when errors happen.
> Impedance mismatch between generic HTTP errors and application defined errors
> notwithstanding, there needs to be a way to differentiate between generic
> HTTP errors, i.e. thrown by Tomcat, and application defined HTTP errors,
> thrown by the Fortress Rest processor.
> ***
> The solution, is to examine the response, in addition to the error code, to
> determine if generic HTTP errors should be thrown, or if normal processing
> should resume.
> {{ case HTTP_404_NOT_FOUND:}}
> {{ szResponse = IOUtils.toString( response.getEntity().getContent(), "UTF-8"
> );}}
> {{ // Crack the response and see if it can be parsed as a valid Fortress
> Response object or generic HTTP:}}
> {{ if( StringUtils.isNotEmpty( szResponse ) &&
> szResponse.contains(VALID_RESPONSE) )}}
> {{ {}}
> {{ LOG.debug( "HTTP: 404: post uri=[{}], function=[{}], response=[{}]",
> uri, function, szResponse );}}
> {{ }}}
> {{ else}}
> {{ {}}
> {{ error = generateErrorMessage( uri, function, "HTTP Error:" +
> response.getStatusLine().getStatusCode());}}
> {{ LOG.error( error );}}
> {{ throw new RestException( GlobalErrIds.REST_NOT_FOUND_ERR, error );}}
> {{ }}}
> {{ break;}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-279) Fix RestUtils error mapping for HTTP errors
[
https://issues.apache.org/jira/browse/FC-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-279:
--
Fix Version/s: (was: 3.0.0-RC1)
2.0.5
> Fix RestUtils error mapping for HTTP errors
> ---
>
> Key: FC-279
> URL: https://issues.apache.org/jira/browse/FC-279
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.5
>
>
> The problem:
> Currently when the URL for Fortress Rest isn't set right, in RestUtils, 404
> error gets masked, as the response is attempted to be parsed.
> Fix the error handing to properly catch http errors and map to appropriate
> exception.
> There's a bit more to this. That is currently Fortress Rest maps application
> defined errors, e.g. read and authentication failures to HTTP error codes, in
> addition to the application status codes.
> The rationale, so certain RESTful clients, i.e. the new Fortress UI don't
> have to crack the message when errors happen.
> Impedance mismatch between generic HTTP errors and application defined errors
> notwithstanding, there needs to be a way to differentiate between generic
> HTTP errors, i.e. thrown by Tomcat, and application defined HTTP errors,
> thrown by the Fortress Rest processor.
> ***
> The solution, is to examine the response, in addition to the error code, to
> determine if generic HTTP errors should be thrown, or if normal processing
> should resume.
> {{ case HTTP_404_NOT_FOUND:}}
> {{ szResponse = IOUtils.toString( response.getEntity().getContent(), "UTF-8"
> );}}
> {{ // Crack the response and see if it can be parsed as a valid Fortress
> Response object or generic HTTP:}}
> {{ if( StringUtils.isNotEmpty( szResponse ) &&
> szResponse.contains(VALID_RESPONSE) )}}
> {{ {}}
> {{ LOG.debug( "HTTP: 404: post uri=[{}], function=[{}], response=[{}]",
> uri, function, szResponse );}}
> {{ }}}
> {{ else}}
> {{ {}}
> {{ error = generateErrorMessage( uri, function, "HTTP Error:" +
> response.getStatusLine().getStatusCode());}}
> {{ LOG.error( error );}}
> {{ throw new RestException( GlobalErrIds.REST_NOT_FOUND_ERR, error );}}
> {{ }}}
> {{ break;}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-280) Verify role constraint exists before assigning to a user
[ https://issues.apache.org/jira/browse/FC-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-280. --- Resolution: Fixed > Verify role constraint exists before assigning to a user > > > Key: FC-280 > URL: https://issues.apache.org/jira/browse/FC-280 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Should prevent user-role constraints from being added if the role constraint > doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-281) [FORTRESS-WEB] Upgrade to Wicket version 8
[ https://issues.apache.org/jira/browse/FC-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-281: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.5 > [FORTRESS-WEB] Upgrade to Wicket version 8 > -- > > Key: FC-281 > URL: https://issues.apache.org/jira/browse/FC-281 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > Bump up to Wicket 8. This requires a change on nearly every page, to change > the way callbacks for Ajax buttons and links. > > Also bump up to latest Spring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-243) [fortress-realm] proxy to use tomcat 9 interface
[ https://issues.apache.org/jira/browse/FC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-243. --- Resolution: Fixed this actually went out with 2.0.4 release > [fortress-realm] proxy to use tomcat 9 interface > > > Key: FC-243 > URL: https://issues.apache.org/jira/browse/FC-243 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1, 2.0.2 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > When updating realm dependencies, > [INFO] org.apache.tomcat:tomcat-catalina ... 7.0.22 -> > 9.0.11 > [ > Get this error on proxy > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 3.884s > [INFO] Finished at: Sat Sep 08 22:30:04 UTC 2018 > [INFO] Final Memory: 24M/239M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) > on project fortress-realm-proxy: Compilation failure: Compilation failure: > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[130,5] > method does not override or implement a method from a supertype > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[133,16] > cannot find symbol > [ERROR] symbol: variable info > [ERROR] location: class > org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[182,5] > method does not override or implement a method from a supertype > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :fortress-realm-proxy > [student@NY1SCOLAPACHE01 directory-fortress-realm]$ -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-243) [fortress-realm] proxy to use tomcat 9 interface
[ https://issues.apache.org/jira/browse/FC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-243: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.4 > [fortress-realm] proxy to use tomcat 9 interface > > > Key: FC-243 > URL: https://issues.apache.org/jira/browse/FC-243 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1, 2.0.2 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.4 > > > When updating realm dependencies, > [INFO] org.apache.tomcat:tomcat-catalina ... 7.0.22 -> > 9.0.11 > [ > Get this error on proxy > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 3.884s > [INFO] Finished at: Sat Sep 08 22:30:04 UTC 2018 > [INFO] Final Memory: 24M/239M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) > on project fortress-realm-proxy: Compilation failure: Compilation failure: > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[130,5] > method does not override or implement a method from a supertype > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[133,16] > cannot find symbol > [ERROR] symbol: variable info > [ERROR] location: class > org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy > [ERROR] > /home/student/apache/fortress/directory-fortress-realm/proxy/src/main/java/org/apache/directory/fortress/realm/tomcat/Tc7AccessMgrProxy.java:[182,5] > method does not override or implement a method from a supertype > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :fortress-realm-proxy > [student@NY1SCOLAPACHE01 directory-fortress-realm]$ -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-276) Correct ant config processing of conditionals like enable ssl or rbac accelerator
[
https://issues.apache.org/jira/browse/FC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-276.
---
Resolution: Fixed
> Correct ant config processing of conditionals like enable ssl or rbac
> accelerator
> -
>
> Key: FC-276
> URL: https://issues.apache.org/jira/browse/FC-276
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.5
>
>
> This problem came up working on rbac accelerator enablement / disablement.
> The conditional:
>
>
>
> This target would execute if this variable was set in the .properties file:
> rbac.accelerator=anything
>
> Correct to only fire when condition is true:
> if="${rbac.accelerator}">
> rbac.accelerator=true
>
> Also made same change for enable.ssl
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-276) Correct ant config processing of conditionals like enable ssl or rbac accelerator
[
https://issues.apache.org/jira/browse/FC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-276:
--
Fix Version/s: (was: 3.0.0-RC1)
2.0.5
> Correct ant config processing of conditionals like enable ssl or rbac
> accelerator
> -
>
> Key: FC-276
> URL: https://issues.apache.org/jira/browse/FC-276
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.5
>
>
> This problem came up working on rbac accelerator enablement / disablement.
> The conditional:
>
>
>
> This target would execute if this variable was set in the .properties file:
> rbac.accelerator=anything
>
> Correct to only fire when condition is true:
> if="${rbac.accelerator}">
> rbac.accelerator=true
>
> Also made same change for enable.ssl
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-282) [FORTRESS-WEB] Make ARBAC checks configurable.
Shawn McKinney created FC-282: - Summary: [FORTRESS-WEB] Make ARBAC checks configurable. Key: FC-282 URL: https://issues.apache.org/jira/browse/FC-282 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.4 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 2.0.5 The Apache Fortress Administrative Role-Based Access Control (ARBAC) subsystem handles delegating administrative tasks to special users. Disabled in FortressWeb by default, to enable, add the following declaration to the fortress.properties: ``` is.arbac02=true ``` -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-282) [FORTRESS-WEB] Make ARBAC checks configurable.
[ https://issues.apache.org/jira/browse/FC-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-282. --- Resolution: Fixed > [FORTRESS-WEB] Make ARBAC checks configurable. > -- > > Key: FC-282 > URL: https://issues.apache.org/jira/browse/FC-282 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.5 > > > The Apache Fortress Administrative Role-Based Access Control (ARBAC) > subsystem handles delegating administrative tasks to special users. > Disabled in FortressWeb by default, to enable, add the following declaration > to the fortress.properties: > ``` > is.arbac02=true > ``` -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-283) Remove property files from quickstart doc
Shawn McKinney created FC-283: - Summary: Remove property files from quickstart doc Key: FC-283 URL: https://issues.apache.org/jira/browse/FC-283 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0 For tests in quickstart guides, use the externallize fortress properties saving trouble of messing with config files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-284) [fortress-core] JDK14 dependency for xml.bind missing
Shawn McKinney created FC-284:
-
Summary: [fortress-core] JDK14 dependency for xml.bind missing
Key: FC-284
URL: https://issues.apache.org/jira/browse/FC-284
Project: FORTRESS
Issue Type: Bug
Affects Versions: 2.0.5
Reporter: Shawn McKinney
Assignee: Shawn McKinney
Fix For: 3.0.0-RC1
Recent editions of the compiler drop the xml.bind dependency. Extend fortress
profile for pulling in the additional dependency to jdk 14 and beyond.
```
jdk-11+
[11,]
javax.xml.bind
jaxb-api
${version.jaxb.api}
```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-284) [fortress-core] JDK14 dependency for xml.bind missing
[
https://issues.apache.org/jira/browse/FC-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-284.
---
Resolution: Fixed
> [fortress-core] JDK14 dependency for xml.bind missing
> -
>
> Key: FC-284
> URL: https://issues.apache.org/jira/browse/FC-284
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> Recent editions of the compiler drop the xml.bind dependency. Extend
> fortress profile for pulling in the additional dependency to jdk 14 and
> beyond.
>
> ```
>
>
> jdk-11+
>
> [11,]
>
>
>
> javax.xml.bind
> jaxb-api
> ${version.jaxb.api}
>
>
>
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-285) [fortress-core]Infinite loop in property interpolation of ${min.log.conn}: min.log.conn
Shawn McKinney created FC-285:
-
Summary: [fortress-core]Infinite loop in property interpolation of
${min.log.conn}: min.log.conn
Key: FC-285
URL: https://issues.apache.org/jira/browse/FC-285
Project: FORTRESS
Issue Type: Bug
Affects Versions: 2.0.5
Reporter: Shawn McKinney
Assignee: Shawn McKinney
Fix For: 3.0.0-RC1
Using the same name for interpolation variable as the property itself creates
an infinite loop if the property is not set.
rename this:
lmin.log.conn=1
max.log.conn=3
to:
*log.min.conn=1*
*log.max.conn=3*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-286) To Apache Log4j 2
Shawn McKinney created FC-286: - Summary: To Apache Log4j 2 Key: FC-286 URL: https://issues.apache.org/jira/browse/FC-286 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Upgrade to Log4j 2, due to vulnerabilities such as: [https://github.com/advisories/GHSA-2qrg-x229-3v8q] in the old libs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-287) Fortress Ant load improvements
Shawn McKinney created FC-287: - Summary: Fortress Ant load improvements Key: FC-287 URL: https://issues.apache.org/jira/browse/FC-287 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney A couple of improvements: 1.Add 'debug' mode, startup load in suspended state, allow JDB process to attach. ``` mvn install -Dload.file=./ldap/setup/loadFile.xml -Ddebug ``` 2. Use maven test classpath instead of classpath element list. Use this: ``` ``` Stop doing this: ``` || || || || | | || || || || || ... ``` -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-287) Fortress Ant load improvements
[
https://issues.apache.org/jira/browse/FC-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-287:
--
Fix Version/s: 2.0.6
> Fortress Ant load improvements
> --
>
> Key: FC-287
> URL: https://issues.apache.org/jira/browse/FC-287
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> A couple of improvements:
> 1.Add 'debug' mode, startup load in suspended state, allow JDB process to
> attach.
> ```
> mvn install -Dload.file=./ldap/setup/loadFile.xml -Ddebug
> ```
>
> 2. Use maven test classpath instead of classpath element list.
>
> Use this:
> ```
> clonevm="true" failonerror="true" dir="${basedir}" timeout="60"
> taskname="startAnt">
>
> ```
>
> Stop doing this:
> ```
> ||
> ||
> | clonevm="true" failonerror="true" dir="${basedir}" timeout="60"
> taskname="startAnt">|
> ||
> | |
> ||
> ||
> ||
> ||
> ||
>
> ...
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-287) Fortress Ant load improvements
[
https://issues.apache.org/jira/browse/FC-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-287.
---
Resolution: Fixed
## SECTION 15. Howto Debug a load script
1. Add -Ddebug=port to runtime args:
```
mvn install -Dload.file=./ldap/setup/refreshLDAPData.xml -Ddebug=5432
```
Which suspends the process waiting for connection on port specified, e.g. 5432.
```
fortress-load-debug:
[echo] ### Run Fortress Ant script to load policy ###
[startAnt] Listening for transport dt_socket at address: 5432
```
2. Set breakpoints in
[FortressAntTask](src/main/java/org/apache/directory/fortress/core/ant/FortressAntTask.java)
3. Connect with the JDB on the specified port.
> Fortress Ant load improvements
> --
>
> Key: FC-287
> URL: https://issues.apache.org/jira/browse/FC-287
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> A couple of improvements:
> 1.Add 'debug' mode, startup load in suspended state, allow JDB process to
> attach.
> ```
> mvn install -Dload.file=./ldap/setup/loadFile.xml -Ddebug
> ```
>
> 2. Use maven test classpath instead of classpath element list.
>
> Use this:
> ```
> clonevm="true" failonerror="true" dir="${basedir}" timeout="60"
> taskname="startAnt">
>
> ```
>
> Stop doing this:
> ```
> ||
> ||
> | clonevm="true" failonerror="true" dir="${basedir}" timeout="60"
> taskname="startAnt">|
> ||
> | |
> ||
> ||
> ||
> ||
> ||
>
> ...
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-288) fix IS_DSD_CACHE_DISABLED_PARM
Shawn McKinney created FC-288: - Summary: fix IS_DSD_CACHE_DISABLED_PARM Key: FC-288 URL: https://issues.apache.org/jira/browse/FC-288 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney maps to incorrectly named fortress.properties: private static final String IS_DSD_CACHE_DISABLED_PARM = "enable.dsd.cache"; change to: private static final String IS_DSD_CACHE_DISABLED_PARM = "disable.dsd.cache"; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-288) fix IS_DSD_CACHE_DISABLED_PARM
[ https://issues.apache.org/jira/browse/FC-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-288. --- Resolution: Fixed > fix IS_DSD_CACHE_DISABLED_PARM > -- > > Key: FC-288 > URL: https://issues.apache.org/jira/browse/FC-288 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > > maps to incorrectly named fortress.properties: > private static final String IS_DSD_CACHE_DISABLED_PARM = "enable.dsd.cache"; > > change to: > private static final String IS_DSD_CACHE_DISABLED_PARM = "disable.dsd.cache"; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-283) Remove property files from quickstart doc
[ https://issues.apache.org/jira/browse/FC-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-283. --- Resolution: Fixed > Remove property files from quickstart doc > - > > Key: FC-283 > URL: https://issues.apache.org/jira/browse/FC-283 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0 > > > For tests in quickstart guides, use the externallize fortress properties > saving trouble of messing with config files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-285) [fortress-core]Infinite loop in property interpolation of ${min.log.conn}: min.log.conn
[
https://issues.apache.org/jira/browse/FC-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-285.
---
Resolution: Fixed
> [fortress-core]Infinite loop in property interpolation of ${min.log.conn}:
> min.log.conn
>
>
> Key: FC-285
> URL: https://issues.apache.org/jira/browse/FC-285
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 3.0.0-RC1
>
>
> Using the same name for interpolation variable as the property itself creates
> an infinite loop if the property is not set.
>
> rename this:
> lmin.log.conn=1
> max.log.conn=3
> to:
> *log.min.conn=1*
> *log.max.conn=3*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-289) fortress-web - get log4j2 working
Shawn McKinney created FC-289: - Summary: fortress-web - get log4j2 working Key: FC-289 URL: https://issues.apache.org/jira/browse/FC-289 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 3.0.0-RC1 Loggers not working with log4j2, this in logs: ``` log4j:WARN No appenders could be found for logger (org.apache.directory.fortress.web.model.UserListModel). log4j:WARN Please initialize the log4j system properly. ``` Change this: ``` import org.apache.log4j.Logger; private static final Logger LOG = Logger.getLogger( ... ); ``` to ``` import org.slf4j.Logger; import org.slf4j.LoggerFactory; private static final Logger LOG = LoggerFactory.getLogger( ... ); ``` -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-289) [fortress-web] get log4j2 working
[ https://issues.apache.org/jira/browse/FC-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-289: -- Summary: [fortress-web] get log4j2 working (was: fortress-web - get log4j2 working) > [fortress-web] get log4j2 working > - > > Key: FC-289 > URL: https://issues.apache.org/jira/browse/FC-289 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > Loggers not working with log4j2, this in logs: > > ``` > log4j:WARN No appenders could be found for logger > (org.apache.directory.fortress.web.model.UserListModel). > log4j:WARN Please initialize the log4j system properly. > ``` > > Change this: > > ``` > import org.apache.log4j.Logger; > private static final Logger LOG = Logger.getLogger( ... ); > ``` > to > ``` > import org.slf4j.Logger; > import org.slf4j.LoggerFactory; > private static final Logger LOG = LoggerFactory.getLogger( ... ); > ``` > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-290) Pool connection validation switch
Shawn McKinney created FC-290:
-
Summary: Pool connection validation switch
Key: FC-290
URL: https://issues.apache.org/jira/browse/FC-290
Project: FORTRESS
Issue Type: Improvement
Affects Versions: 2.0.5
Reporter: Shawn McKinney
Assignee: Shawn McKinney
Fix For: 2.0.6
Currently a dummy search is made to server every time a connection is retrieved
from the pool.
This behavior needs to be made configurable via adding a switch to the
connection pool creation, in LdapConnectionProvider class via the
setTestOnBorrow method:
{color:#00}```{color}
{color:#00}// Create the Admin pool{color}
{color:#00}adminPool = new LdapConnectionPool( poolFactory );{color}
{color:#00}adminPool.setTestOnBorrow( true );{color}
{color:#00}adminPool.setWhenExhaustedAction(
GenericObjectPool.WHEN_EXHAUSTED_GROW );{color}
{color:#00}adminPool.setMaxActive( max );{color}
{color:#00}adminPool.setMinIdle( min );{color}
{color:#00}adminPool.setMaxIdle( -1 );{color}
{color:#00}adminPool.setTestWhileIdle( testWhileIdle );{color}
{color:#00}adminPool.setTimeBetweenEvictionRunsMillis(
timeBetweenEvictionRunMillis );{color}
{color:#00}```{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-290) Pool connection validation switch
[
https://issues.apache.org/jira/browse/FC-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308700#comment-17308700
]
Shawn McKinney commented on FC-290:
---
It has been determined that the ldap search on borrowed and idle connections is
not necessary because bad connections will be reconnected on the borrow
automatically.
Follow link for more info:
https://lists.apache.org/thread.html/r37e35466dfb859e0dd75b9cbce70b5e423ad2d7e884ff974f9710284%40%3Capi.directory.apache.org%3E
> Pool connection validation switch
> -
>
> Key: FC-290
> URL: https://issues.apache.org/jira/browse/FC-290
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> Currently a dummy search is made to server every time a connection is
> retrieved from the pool.
>
> This behavior needs to be made configurable via adding a switch to the
> connection pool creation, in LdapConnectionProvider class via the
> setTestOnBorrow method:
> {color:#00}```{color}
> {color:#00}// Create the Admin pool{color}
> {color:#00}adminPool = new LdapConnectionPool( poolFactory );{color}
> {color:#00}adminPool.setTestOnBorrow( true );{color}
> {color:#00}adminPool.setWhenExhaustedAction(
> GenericObjectPool.WHEN_EXHAUSTED_GROW );{color}
> {color:#00}adminPool.setMaxActive( max );{color}
> {color:#00}adminPool.setMinIdle( min );{color}
> {color:#00}adminPool.setMaxIdle( -1 );{color}
> {color:#00}adminPool.setTestWhileIdle( testWhileIdle );{color}
> {color:#00}adminPool.setTimeBetweenEvictionRunsMillis(
> timeBetweenEvictionRunMillis );{color}
> {color:#00}```{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-290) Pool connection validation switch
[
https://issues.apache.org/jira/browse/FC-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308701#comment-17308701
]
Shawn McKinney commented on FC-290:
---
Added properties to control this behavior:
```
# Applies to all pools, connection validated on retrieval with dummy
ldapsearch. (default is false)
all.validate.conn.borrow=false
# Applies to all pools, connection validated when idle with dummy ldapsearch.
(default is false)
all.validate.conn.idle=false
```
> Pool connection validation switch
> -
>
> Key: FC-290
> URL: https://issues.apache.org/jira/browse/FC-290
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> Currently a dummy search is made to server every time a connection is
> retrieved from the pool.
>
> This behavior needs to be made configurable via adding a switch to the
> connection pool creation, in LdapConnectionProvider class via the
> setTestOnBorrow method:
> {color:#00}```{color}
> {color:#00}// Create the Admin pool{color}
> {color:#00}adminPool = new LdapConnectionPool( poolFactory );{color}
> {color:#00}adminPool.setTestOnBorrow( true );{color}
> {color:#00}adminPool.setWhenExhaustedAction(
> GenericObjectPool.WHEN_EXHAUSTED_GROW );{color}
> {color:#00}adminPool.setMaxActive( max );{color}
> {color:#00}adminPool.setMinIdle( min );{color}
> {color:#00}adminPool.setMaxIdle( -1 );{color}
> {color:#00}adminPool.setTestWhileIdle( testWhileIdle );{color}
> {color:#00}adminPool.setTimeBetweenEvictionRunsMillis(
> timeBetweenEvictionRunMillis );{color}
> {color:#00}```{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Comment Edited] (FC-290) Pool connection validation switch
[
https://issues.apache.org/jira/browse/FC-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308701#comment-17308701
]
Shawn McKinney edited comment on FC-290 at 3/25/21, 2:03 PM:
-
Added properties to control this behavior:
```
#Applies to all pools, connection validated on retrieval with dummy ldapsearch.
(default is false)
all.validate.conn.borrow=false
#Applies to all pools, connection validated when idle with dummy ldapsearch.
(default is false)
all.validate.conn.idle=false
```
was (Author: smckinney):
Added properties to control this behavior:
```
# Applies to all pools, connection validated on retrieval with dummy
ldapsearch. (default is false)
all.validate.conn.borrow=false
# Applies to all pools, connection validated when idle with dummy ldapsearch.
(default is false)
all.validate.conn.idle=false
```
> Pool connection validation switch
> -
>
> Key: FC-290
> URL: https://issues.apache.org/jira/browse/FC-290
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> Currently a dummy search is made to server every time a connection is
> retrieved from the pool.
>
> This behavior needs to be made configurable via adding a switch to the
> connection pool creation, in LdapConnectionProvider class via the
> setTestOnBorrow method:
> {color:#00}```{color}
> {color:#00}// Create the Admin pool{color}
> {color:#00}adminPool = new LdapConnectionPool( poolFactory );{color}
> {color:#00}adminPool.setTestOnBorrow( true );{color}
> {color:#00}adminPool.setWhenExhaustedAction(
> GenericObjectPool.WHEN_EXHAUSTED_GROW );{color}
> {color:#00}adminPool.setMaxActive( max );{color}
> {color:#00}adminPool.setMinIdle( min );{color}
> {color:#00}adminPool.setMaxIdle( -1 );{color}
> {color:#00}adminPool.setTestWhileIdle( testWhileIdle );{color}
> {color:#00}adminPool.setTimeBetweenEvictionRunsMillis(
> timeBetweenEvictionRunMillis );{color}
> {color:#00}```{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-290) Pool connection validation switch
[
https://issues.apache.org/jira/browse/FC-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-290.
---
Resolution: Fixed
> Pool connection validation switch
> -
>
> Key: FC-290
> URL: https://issues.apache.org/jira/browse/FC-290
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> Currently a dummy search is made to server every time a connection is
> retrieved from the pool.
>
> This behavior needs to be made configurable via adding a switch to the
> connection pool creation, in LdapConnectionProvider class via the
> setTestOnBorrow method:
> {color:#00}```{color}
> {color:#00}// Create the Admin pool{color}
> {color:#00}adminPool = new LdapConnectionPool( poolFactory );{color}
> {color:#00}adminPool.setTestOnBorrow( true );{color}
> {color:#00}adminPool.setWhenExhaustedAction(
> GenericObjectPool.WHEN_EXHAUSTED_GROW );{color}
> {color:#00}adminPool.setMaxActive( max );{color}
> {color:#00}adminPool.setMinIdle( min );{color}
> {color:#00}adminPool.setMaxIdle( -1 );{color}
> {color:#00}adminPool.setTestWhileIdle( testWhileIdle );{color}
> {color:#00}adminPool.setTimeBetweenEvictionRunsMillis(
> timeBetweenEvictionRunMillis );{color}
> {color:#00}```{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-291) Support Relax Control
Shawn McKinney created FC-291: - Summary: Support Relax Control Key: FC-291 URL: https://issues.apache.org/jira/browse/FC-291 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.5 Reporter: Shawn McKinney Assignee: Shawn McKinney Fix For: 2.0.4 OpenLDAP now enforces RFC on pw policy attribute mod of operational attributes like pwdLockout and pwdPolicySubentry. This requires sending the following control: The LDAP Relax Rules Control [https://tools.ietf.org/html/draft-zeilenga-ldap-relax-03] String OID = "1.3.6.1.4.1.4203.666.5.12"; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (FC-292) User displayName attribute not updated
[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-292: - Assignee: Shawn McKinney The patch does the following: # create - will use what's contained in displayName attribute if not empty, otherwise cn # modify - will update attribute, if not empty # unloadLdapEntry - load the contents pulled back from entry I'm good with these changes, although I couldn't get the patch to work, so I'll just make the coding changes for you. Thanks! > User displayName attribute not updated > -- > > Key: FC-292 > URL: https://issues.apache.org/jira/browse/FC-292 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Admir Hodzic >Assignee: Shawn McKinney >Priority: Minor > Attachments: UserDisplayNameUpdate.patch > > > User displayName attribute is not getting updated by a call to > AdminMgr.updateUser. > I have created a small patch to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-292) User displayName attribute not updated
[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-292: -- Fix Version/s: 2.0.6 > User displayName attribute not updated > -- > > Key: FC-292 > URL: https://issues.apache.org/jira/browse/FC-292 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Admir Hodzic >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.6 > > Attachments: UserDisplayNameUpdate.patch > > > User displayName attribute is not getting updated by a call to > AdminMgr.updateUser. > I have created a small patch to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-293) [fortress-web] CVE-2020-11976
Shawn McKinney created FC-293: - Summary: [fortress-web] CVE-2020-11976 Key: FC-293 URL: https://issues.apache.org/jira/browse/FC-293 Project: FORTRESS Issue Type: Improvement Reporter: Shawn McKinney h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] high severity *Vulnerable versions:* >= 8.0.0, < 8.9.0 *Patched version:* 8.9.0 By crafting a special URL it is possible to make Wicket deliver unprocessed HTML templates. This would allow an attacker to see possibly sensitive information inside a HTML template that is usually removed during rendering. Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-293. - Resolution: Fixed > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Reporter: Shawn McKinney >Priority: Major > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-294) combine jmeter load profiles
Shawn McKinney created FC-294:
-
Summary: combine jmeter load profiles
Key: FC-294
URL: https://issues.apache.org/jira/browse/FC-294
Project: FORTRESS
Issue Type: Improvement
Affects Versions: 2.0.5
Reporter: Shawn McKinney
Assignee: Shawn McKinney
Fix For: 2.0.6
Currently 9 maven profiles for load testing. Combine into one or at most two.
Current:
```
# execute adduser load test:
mvn -Ploadtest-fortress-adduser jmeter:jmeter ...
# configure ftAddUser.jmx
loadtest-fortress-checkuser
ftAddUser.jmx
```
Replaced with:
```
mvn -Ploadtest jmeter:jmeter -Dtype=addUser ...
loadtest
${type}.jmx
```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-294) combine jmeter load profiles
[
https://issues.apache.org/jira/browse/FC-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-294.
---
Resolution: Fixed
> combine jmeter load profiles
>
>
> Key: FC-294
> URL: https://issues.apache.org/jira/browse/FC-294
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Minor
> Fix For: 2.0.6
>
>
> Currently 9 maven profiles for load testing. Combine into one or at most two.
>
> Current:
>
> ```
> execute adduser load test:
> mvn -Ploadtest-fortress-adduser jmeter:jmeter ...
>
> configure ftAddUser.jmx
>
> loadtest-fortress-checkuser
>
>
> ftAddUser.jmx
> ```
> Replaced with:
> ```
> mvn -Ploadtest jmeter:jmeter -Dtype=addUser ...
>
>
> loadtest
>
>
>
>
> ${type}.jmx
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-294) combine jmeter load profiles
[
https://issues.apache.org/jira/browse/FC-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-294:
--
Description:
Currently 9 maven profiles for load testing. Combine into one or at most two.
Current:
```
execute adduser load test:
mvn -Ploadtest-fortress-adduser jmeter:jmeter ...
configure ftAddUser.jmx
loadtest-fortress-checkuser
ftAddUser.jmx
```
Replaced with:
```
mvn -Ploadtest jmeter:jmeter -Dtype=addUser ...
loadtest
${type}.jmx
```
was:
Currently 9 maven profiles for load testing. Combine into one or at most two.
Current:
```
# execute adduser load test:
mvn -Ploadtest-fortress-adduser jmeter:jmeter ...
# configure ftAddUser.jmx
loadtest-fortress-checkuser
ftAddUser.jmx
```
Replaced with:
```
mvn -Ploadtest jmeter:jmeter -Dtype=addUser ...
loadtest
${type}.jmx
```
> combine jmeter load profiles
>
>
> Key: FC-294
> URL: https://issues.apache.org/jira/browse/FC-294
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Minor
> Fix For: 2.0.6
>
>
> Currently 9 maven profiles for load testing. Combine into one or at most two.
>
> Current:
>
> ```
> execute adduser load test:
> mvn -Ploadtest-fortress-adduser jmeter:jmeter ...
>
> configure ftAddUser.jmx
>
> loadtest-fortress-checkuser
>
>
> ftAddUser.jmx
> ```
> Replaced with:
> ```
> mvn -Ploadtest jmeter:jmeter -Dtype=addUser ...
>
>
> loadtest
>
>
>
>
> ${type}.jmx
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (FC-238) Migrate to LDAP API 2.0
[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-238: - Assignee: Shawn McKinney (was: Emmanuel Lécharny) > Migrate to LDAP API 2.0 > --- > > Key: FC-238 > URL: https://issues.apache.org/jira/browse/FC-238 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 3.0.0-RC1 > > > The code compiles, but gets NPE when fortress tries to open a pool to the > server > ** > Steps to recreate. > # Get fortress env, checkout latest, follow the steps in DOCKER README to > get either openldap or apacheds server up. > # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file= > ## in order to verify the env is running correctly run this test: > ### mvn test -Pconsole <-– should be no errors > # Now checkout the code that is using ldap api 2.0.0 > ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000 > # connect with fortress console: > ## mvn test -Pconsole > Get the error: > > 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 - > MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4) > [WARNING] > org.apache.directory.fortress.core.CfgRuntimeException: Exception caught > initializing Admin Pool: java.lang.NullPointerException, errCode=135 > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103) > at > org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215) > at > org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327) > at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175) > at > org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102) > at > org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377) > at > org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655) > at > org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101) > at > org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68) > at > org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74) > at > org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38) > at > org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313) > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180) > ... 19 more > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-238) Migrate to LDAP API 2.0
[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-238: -- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 > Migrate to LDAP API 2.0 > --- > > Key: FC-238 > URL: https://issues.apache.org/jira/browse/FC-238 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > The code compiles, but gets NPE when fortress tries to open a pool to the > server > ** > Steps to recreate. > # Get fortress env, checkout latest, follow the steps in DOCKER README to > get either openldap or apacheds server up. > # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file= > ## in order to verify the env is running correctly run this test: > ### mvn test -Pconsole <-– should be no errors > # Now checkout the code that is using ldap api 2.0.0 > ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000 > # connect with fortress console: > ## mvn test -Pconsole > Get the error: > > 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 - > MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4) > [WARNING] > org.apache.directory.fortress.core.CfgRuntimeException: Exception caught > initializing Admin Pool: java.lang.NullPointerException, errCode=135 > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103) > at > org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215) > at > org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327) > at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175) > at > org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102) > at > org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377) > at > org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655) > at > org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101) > at > org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68) > at > org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74) > at > org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38) > at > org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313) > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180) > ... 19 more > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367342#comment-17367342
]
Shawn McKinney commented on FC-238:
---
Renewing this work. Here are the problem areas:
1. LDAP connection pool (LdapConnectionProvider)
PooledObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//PoolableObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//adminPool.setWhenExhaustedAction(
GenericObjectPool.WHEN_EXHAUSTED_GROW );
//adminPool.setMaxActive( max );
2. Relax Control (LdapDataProvider)
if ( setRelaxControl )
{
addRequest.addControl( new RelaxControlImpl() );
}
: ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
2021-06-21 17:05:027 WARN LdapNetworkConnection:2478 -
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
org.apache.mina.filter.codec.ProtocolEncoderException:
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
3. PW Policy Control (LdapDataProvider)
protected PasswordPolicy getPwdRespCtrl(Response resp )
{
//Control control = resp.getControls().get( PP_REQ_CTRL.getOid() );
Control control = resp.getControls().get( "1.3.6.1.4.1.42.2.27.8.5.1" );
if ( control == null )
{
return null;
}
return ( ( PasswordPolicyDecorator ) control ).getDecorated();
}
4. RBAC Accelerator Extended Ops (LdapConnectionProvider)
List listExOps = new ArrayList<>();
listExOps.add(
"org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.checkAccess.RbacCheckAccessFactory" );
listExOps.add(
"org.openldap.accelerator.impl.addRole.RbacAddRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.dropRole.RbacDropRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.deleteSession.RbacDeleteSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.sessionRoles.RbacSessionRolesFactory" );
LdapApiService ldapApiService = new StandaloneLdapApiService( new
ArrayList(), listExOps );
if ( !LdapApiServiceFactory.isInitialized() )
{
LdapApiServiceFactory.initialize( ldapApiService );
}
config.setLdapApiService( ldapApiService );
> Migrate to LDAP API 2.0
> ---
>
> Key: FC-238
> URL: https://issues.apache.org/jira/browse/FC-238
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> The code compiles, but gets NPE when fortress tries to open a pool to the
> server
> **
> Steps to recreate.
> # Get fortress env, checkout latest, follow the steps in DOCKER README to
> get either openldap or apacheds server up.
> # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file=
> ## in order to verify the env is running correctly run this test:
> ### mvn test -Pconsole <-– should be no errors
> # Now checkout the code that is using ldap api 2.0.0
> ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000
> # connect with fortress console:
> ## mvn test -Pconsole
> Get the error:
>
> 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 -
> MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4)
> [WARNING]
> org.apache.directory.fortress.core.CfgRuntimeException: Exception caught
> initializing Admin Pool: java.lang.NullPointerException, errCode=135
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103)
> at
> org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215)
> at
> org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327)
> at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175)
> at
> org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102)
> at
> org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377)
> at
> org.apache.directory.fortress.core.ut
[jira] [Comment Edited] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367342#comment-17367342
]
Shawn McKinney edited comment on FC-238 at 6/22/21, 4:04 PM:
-
Renewing this work. Here are the problem areas:
1. LDAP connection pool (LdapConnectionProvider)
PooledObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//PoolableObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//adminPool.setWhenExhaustedAction(
GenericObjectPool.WHEN_EXHAUSTED_GROW );
//adminPool.setMaxActive( max );
// have substituted with these:
adminPool.setMaxTotal( max );
adminPool.setBlockWhenExhausted( true );
adminPool.setMaxWaitMillis( 5000 );
2. Relax Control (LdapDataProvider)
if ( setRelaxControl )
{
addRequest.addControl( new RelaxControlImpl() );
}
: ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
2021-06-21 17:05:027 WARN LdapNetworkConnection:2478 -
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
org.apache.mina.filter.codec.ProtocolEncoderException:
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
3. PW Policy Control (LdapDataProvider)
protected PasswordPolicy getPwdRespCtrl(Response resp )
{
//Control control = resp.getControls().get( PP_REQ_CTRL.getOid() );
Control control = resp.getControls().get( "1.3.6.1.4.1.42.2.27.8.5.1" );
if ( control == null )
{
return null;
}
return ( ( PasswordPolicyDecorator ) control ).getDecorated();
}
4. RBAC Accelerator Extended Ops (LdapConnectionProvider)
List listExOps = new ArrayList<>();
listExOps.add(
"org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.checkAccess.RbacCheckAccessFactory" );
listExOps.add(
"org.openldap.accelerator.impl.addRole.RbacAddRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.dropRole.RbacDropRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.deleteSession.RbacDeleteSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.sessionRoles.RbacSessionRolesFactory" );
LdapApiService ldapApiService = new StandaloneLdapApiService( new
ArrayList(), listExOps );
if ( !LdapApiServiceFactory.isInitialized() )
{
LdapApiServiceFactory.initialize( ldapApiService );
}
config.setLdapApiService( ldapApiService );
was (Author: smckinney):
Renewing this work. Here are the problem areas:
1. LDAP connection pool (LdapConnectionProvider)
PooledObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//PoolableObjectFactory poolFactory = new
ValidatingPoolableLdapConnectionFactory( config );
//adminPool.setWhenExhaustedAction(
GenericObjectPool.WHEN_EXHAUSTED_GROW );
//adminPool.setMaxActive( max );
2. Relax Control (LdapDataProvider)
if ( setRelaxControl )
{
addRequest.addControl( new RelaxControlImpl() );
}
: ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
2021-06-21 17:05:027 WARN LdapNetworkConnection:2478 -
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
org.apache.mina.filter.codec.ProtocolEncoderException:
org.apache.directory.api.asn1.EncoderException:
ERR_08002_CANNOT_FIND_CONTROL_FACTORY failed to find a control factory for
control OID: 1.3.6.1.4.1.4203.666.5.12
3. PW Policy Control (LdapDataProvider)
protected PasswordPolicy getPwdRespCtrl(Response resp )
{
//Control control = resp.getControls().get( PP_REQ_CTRL.getOid() );
Control control = resp.getControls().get( "1.3.6.1.4.1.42.2.27.8.5.1" );
if ( control == null )
{
return null;
}
return ( ( PasswordPolicyDecorator ) control ).getDecorated();
}
4. RBAC Accelerator Extended Ops (LdapConnectionProvider)
List listExOps = new ArrayList<>();
listExOps.add(
"org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.checkAccess.RbacCheckAccessFactory" );
listExOps.add(
"org.openldap.accelerator.impl
[jira] [Commented] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368407#comment-17368407
]
Shawn McKinney commented on FC-238:
---
3. PW Policy Control (LdapDataProvider)
Follow this test example:
[AbstractPasswordPolicyResponder](https://github.com/apache/directory-ldap-api/blob/master/ldap/client/api/src/main/java/org/apache/directory/ldap/client/template/AbstractPasswordPolicyResponder.java)
Processing response control like this:
```
protected PasswordPolicyResponse getPwdRespCtrl(BindResponse resp )
{
Control control = resp.getControls().get( PasswordPolicyResponse.OID );
return ( PasswordPolicyResponse ) control;
}
```
And then coaxing out the info is straightforward:
```
if ( respCtrl != null ){
…
if ( respCtrl.getTimeBeforeExpiration() > 0 ){
…
}
if ( respCtrl.getGraceAuthNRemaining() > 0 ){
…
}
```
> Migrate to LDAP API 2.0
> ---
>
> Key: FC-238
> URL: https://issues.apache.org/jira/browse/FC-238
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> The code compiles, but gets NPE when fortress tries to open a pool to the
> server
> **
> Steps to recreate.
> # Get fortress env, checkout latest, follow the steps in DOCKER README to
> get either openldap or apacheds server up.
> # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file=
> ## in order to verify the env is running correctly run this test:
> ### mvn test -Pconsole <-– should be no errors
> # Now checkout the code that is using ldap api 2.0.0
> ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000
> # connect with fortress console:
> ## mvn test -Pconsole
> Get the error:
>
> 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 -
> MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4)
> [WARNING]
> org.apache.directory.fortress.core.CfgRuntimeException: Exception caught
> initializing Admin Pool: java.lang.NullPointerException, errCode=135
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103)
> at
> org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215)
> at
> org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327)
> at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175)
> at
> org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102)
> at
> org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377)
> at
> org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655)
> at
> org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101)
> at
> org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68)
> at
> org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74)
> at
> org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38)
> at
> org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313)
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180)
> ... 19 more
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369008#comment-17369008
]
Shawn McKinney commented on FC-238:
---
3. here's how to retrieve the control:
protected PasswordPolicyResponse getPwdRespCtrl(BindResponse resp )
{
return ( PasswordPolicyResponse ) resp.getControls().get(
PasswordPolicyRequest.OID );
}
> Migrate to LDAP API 2.0
> ---
>
> Key: FC-238
> URL: https://issues.apache.org/jira/browse/FC-238
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> The code compiles, but gets NPE when fortress tries to open a pool to the
> server
> **
> Steps to recreate.
> # Get fortress env, checkout latest, follow the steps in DOCKER README to
> get either openldap or apacheds server up.
> # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file=
> ## in order to verify the env is running correctly run this test:
> ### mvn test -Pconsole <-– should be no errors
> # Now checkout the code that is using ldap api 2.0.0
> ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000
> # connect with fortress console:
> ## mvn test -Pconsole
> Get the error:
>
> 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 -
> MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4)
> [WARNING]
> org.apache.directory.fortress.core.CfgRuntimeException: Exception caught
> initializing Admin Pool: java.lang.NullPointerException, errCode=135
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103)
> at
> org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215)
> at
> org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327)
> at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175)
> at
> org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102)
> at
> org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377)
> at
> org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655)
> at
> org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101)
> at
> org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68)
> at
> org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74)
> at
> org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38)
> at
> org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313)
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180)
> ... 19 more
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369014#comment-17369014
]
Shawn McKinney commented on FC-238:
---
2. Relax Control (LdapDataProvider)
Two part solution:
a. add / register the control in the API.
https://github.com/apache/directory-ldap-api/commit/12353c1487412b0c7e0d36a68297ab713dd0
b. until next release of API, need to leave control in fortress and register it
like this:
```
if ( Config.getInstance().getBoolean(
"enable.relax.control.registration", false ) )
{
ControlFactory relaxControlFactory = new
RelaxControlFactory( new DefaultLdapCodecService() );
(new
LdapNetworkConnection()).getCodecService().registerRequestControl(relaxControlFactory);
LOG.info( "Register RelaxControl" );
}
```
so that it will be found by the runtime.
Once 2.0.3 is released, the corresponding fortress code can be removed.
> Migrate to LDAP API 2.0
> ---
>
> Key: FC-238
> URL: https://issues.apache.org/jira/browse/FC-238
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> The code compiles, but gets NPE when fortress tries to open a pool to the
> server
> **
> Steps to recreate.
> # Get fortress env, checkout latest, follow the steps in DOCKER README to
> get either openldap or apacheds server up.
> # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file=
> ## in order to verify the env is running correctly run this test:
> ### mvn test -Pconsole <-– should be no errors
> # Now checkout the code that is using ldap api 2.0.0
> ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000
> # connect with fortress console:
> ## mvn test -Pconsole
> Get the error:
>
> 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 -
> MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4)
> [WARNING]
> org.apache.directory.fortress.core.CfgRuntimeException: Exception caught
> initializing Admin Pool: java.lang.NullPointerException, errCode=135
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103)
> at
> org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215)
> at
> org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327)
> at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175)
> at
> org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102)
> at
> org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377)
> at
> org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655)
> at
> org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101)
> at
> org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68)
> at
> org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74)
> at
> org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38)
> at
> org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313)
> at
> org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180)
> ... 19 more
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-238) Migrate to LDAP API 2.0
[
https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369035#comment-17369035
]
Shawn McKinney commented on FC-238:
---
4. RBAC Accelerator Extended Ops (LdapConnectionProvider)
change constructor from:
```
LdapApiService ldapApiService = new StandaloneLdapApiService( new
ArrayList(), listExOps );
```
to:
```
LdapApiService ldapApiService = new StandaloneLdapApiService( new
ArrayList(), new ArrayList(), listExOps, new
ArrayList() );
```
code compiles and runs but when making accelerator extended operations
server-side assertion fails:
```
[exec] 60d4c866 <= send_search_entry: conn 1000 exit.
[exec] 60d4c866 send_ldap_result: conn=1000 op=1 p=3
[exec] 60d4c866 send_ldap_result: err=0 matched="" text=""
[exec] 60d4c866 send_ldap_response: msgid=2 tag=101 err=0
[exec] ber_flush2: 14 bytes to sd 23
[exec] : 30 0c 02 01 02 65 07 0a 01 00 04 00 04 00
0e
[exec] ldap_write: want=14, written=14
[exec] : 30 0c 02 01 02 65 07 0a 01 00 04 00 04 00
0e
[exec] 60d4c866 conn=1000 op=1 SEARCH RESULT tag=101 err=0 qtime=0.45
etime=0.197924 nentries=1 text=
[exec] 60d4c866 daemon: activity on 1 descriptor
[exec] 60d4c866 daemon: activity on: 23r
[exec] 60d4c866 daemon: read active on 23
[exec] 60d4c866 daemon: epoll: listen=7 active_threads=0 tvp=zero
[exec] 60d4c866 connection_get(23)
[exec] 60d4c866 connection_get(23): got connid=1000
[exec] 60d4c866 connection_read(23): checking for input on id=1000
[exec] ber_get_next
[exec] ldap_read: want=8, got=8
[exec] : 30 1d 02 01 03 77 18 80
0w..
[exec] ldap_read: want=23, got=23
[exec] : 16 31 2e 33 2e 36 2e 31 2e 34 2e 31 2e 34 32 30
.1.3.6.1.4.1.420
[exec] 0010: 33 2e 35 35 35 2e 31 3.555.1
[exec] ber_get_next: tag 0x30 len 29 contents:
[exec] ber_dump: buf=0x7fdc8b60 ptr=0x7fdc8b60 end=0x7fdc8b7d
len=29
[exec] : 02 01 03 77 18 80 16 31 2e 33 2e 36 2e 31 2e 34
...w...1.3.6.1.4
[exec] 0010: 2e 31 2e 34 32 30 33 2e 35 35 35 2e 31
.1.4203.555.1
[exec] 60d4c866 op tag 0x77, time 1624557670
[exec] ber_get_next
[exec] ldap_read: want=8 error=Resource temporarily unavailable
[exec] 60d4c866 daemon: activity on 1 descriptor
[exec] 60d4c866 daemon: activity on:60d4c866 conn=1000 op=2 do_extended
[exec] ber_scanf fmt ({m) ber:
[exec] ber_dump: buf=0x7fdc8b60 ptr=0x7fdc8b63 end=0x7fdc8b7d
len=26
[exec] : 77 18 80 16 31 2e 33 2e 36 2e 31 2e 34 2e 31 2e
w...1.3.6.1.4.1.
[exec] 0010: 34 32 30 33 2e 35 35 35 2e 31
4203.555.1
[exec] 60d4c866 conn=1000 op=2 EXT oid=1.3.6.1.4.1.4203.555.1
[exec] 60d4c866 do_extended: oid=1.3.6.1.4.1.4203.555.1
[exec] 60d4c866 rbac_create_session entry
[exec] slapd: /home/build/sold/slapo-rbac/overlay/rbac.c:816:
rbac_create_session: Assertion `rs->sr_err == LDAP_SUCCESS' failed.
[exec] Aborted (core dumped)
[exec] Result: 134
```
> Migrate to LDAP API 2.0
> ---
>
> Key: FC-238
> URL: https://issues.apache.org/jira/browse/FC-238
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> The code compiles, but gets NPE when fortress tries to open a pool to the
> server
> **
> Steps to recreate.
> # Get fortress env, checkout latest, follow the steps in DOCKER README to
> get either openldap or apacheds server up.
> # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file=
> ## in order to verify the env is running correctly run this test:
> ### mvn test -Pconsole <-– should be no errors
> # Now checkout the code that is using ldap api 2.0.0
> ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000
> # connect with fortress console:
> ## mvn test -Pconsole
> Get the error:
>
> 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 -
> MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4)
> [WARNING]
> org.apache.directory.fortress.core.CfgRuntimeException: Exception caught
> initializing Admin Pool: java.lang.NullPointerException, errCode=135
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116)
> at
> org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103
[jira] [Reopened] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reopened FC-293: --- Assignee: Shawn McKinney > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Fix Version/s: 2.0.6 > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-291) Support Relax Control
[ https://issues.apache.org/jira/browse/FC-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-291: -- Fix Version/s: (was: 2.0.4) 2.0.6 > Support Relax Control > - > > Key: FC-291 > URL: https://issues.apache.org/jira/browse/FC-291 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > OpenLDAP now enforces RFC on pw policy attribute mod of operational > attributes like pwdLockout and pwdPolicySubentry. > This requires sending the following control: > The LDAP Relax Rules Control > [https://tools.ietf.org/html/draft-zeilenga-ldap-relax-03] > String OID = "1.3.6.1.4.1.4203.666.5.12"; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Affects Version/s: 2.0.4 > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.4 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-293. - > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-293: -- Affects Version/s: (was: 2.0.4) 2.0.5 > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-293) [fortress-web] CVE-2020-11976
[ https://issues.apache.org/jira/browse/FC-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-293. --- Resolution: Fixed > [fortress-web] CVE-2020-11976 > - > > Key: FC-293 > URL: https://issues.apache.org/jira/browse/FC-293 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > h5. [CVE-2020-11976|https://github.com/advisories/GHSA-64gv-3pqv-299h] > high severity > *Vulnerable versions:* >= 8.0.0, < 8.9.0 > *Patched version:* 8.9.0 > By crafting a special URL it is possible to make Wicket deliver unprocessed > HTML templates. This would allow an attacker to see possibly sensitive > information inside a HTML template that is usually removed during rendering. > Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (FC-244) [fortress-core] builds fail in Java 11
[
https://issues.apache.org/jira/browse/FC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney closed FC-244.
-
Resolution: Not A Bug
> [fortress-core] builds fail in Java 11
> --
>
> Key: FC-244
> URL: https://issues.apache.org/jira/browse/FC-244
> Project: FORTRESS
> Issue Type: Improvement
>Affects Versions: 2.0.1
>Reporter: Shawn McKinney
>Priority: Major
>
> {color:#00}Build of fortress-core with Java 11+ea25 fails because
> java.xml.bind {color}{color:#00}is no longer part of JDK.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-292) User displayName attribute not updated
[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-292. --- Resolution: Fixed > User displayName attribute not updated > -- > > Key: FC-292 > URL: https://issues.apache.org/jira/browse/FC-292 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Admir Hodzic >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.6 > > Attachments: UserDisplayNameUpdate.patch > > > User displayName attribute is not getting updated by a call to > AdminMgr.updateUser. > I have created a small patch to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-291) Support Relax Control
[ https://issues.apache.org/jira/browse/FC-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-291. --- Resolution: Fixed > Support Relax Control > - > > Key: FC-291 > URL: https://issues.apache.org/jira/browse/FC-291 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > OpenLDAP now enforces RFC on pw policy attribute mod of operational > attributes like pwdLockout and pwdPolicySubentry. > This requires sending the following control: > The LDAP Relax Rules Control > [https://tools.ietf.org/html/draft-zeilenga-ldap-relax-03] > String OID = "1.3.6.1.4.1.4203.666.5.12"; -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (FC-262) Add tmeout configuration for connection pools
[ https://issues.apache.org/jira/browse/FC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369886#comment-17369886 ] Shawn McKinney commented on FC-262: --- This issue needs a description as to what timeout values are missing from pool. > Add tmeout configuration for connection pools > - > > Key: FC-262 > URL: https://issues.apache.org/jira/browse/FC-262 > Project: FORTRESS > Issue Type: Improvement >Reporter: Chris Pike >Assignee: Chris Pike >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (FC-258) Updating the way FortResponse is served
[
https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney closed FC-258.
-
> Updating the way FortResponse is served
> ---
>
> Key: FC-258
> URL: https://issues.apache.org/jira/browse/FC-258
> Project: FORTRESS
> Issue Type: Bug
>Reporter: Kiran Ayyagari
>Assignee: Kiran Ayyagari
>Priority: Major
>
> The FortResponse instance created as a result of operation exception is still
> sent to the client with a HTTP status code of "200 OK" forcing clients to
> rely on the {{errorCode}} field to figure out the actual status of the
> operation.
> For example when the below request is sent to a stock Fortress REST service
> {code}
> curl -POST http://localhost:7070/fortress-rest/userAdd --header
> "Content-Type: application/json" --header "Accept: application/json" --header
> "Authorization: Basic dGVzdDpwYXNzd29yZA==" -v -d '{ "entity": { "fqcn":
> "org.apache.directory.fortress.core.model.User", "userId": "test1", "ou":
> "non-existing-ou" }, "contextId": "HOME" }'
> {code}
> the below success response is received though the request was failed due to a
> validation error which ideally should have been responded with a "400 bad
> request" error.
> {code}
> * Trying ::1...
> * TCP_NODELAY set
> * Connected to localhost (::1) port 7070 (#0)
> > POST /fortress-rest/userAdd HTTP/1.1
> > Host: localhost:7070
> > User-Agent: curl/7.54.0
> > Content-Type: application/json
> > Accept: application/json
> > Authorization: Basic dGVzdDpwYXNzd29yZA==
> > Content-Length: 138
> >
> * upload completely sent off: 138 out of 138 bytes
> < HTTP/1.1 200
> < Date: Fri, 16 Nov 2018 15:05:04 GMT
> < Content-Type: application/json
> < Transfer-Encoding: chunked
> <
> * Connection #0 to host localhost left intact
> {"errorCode":1035,"isAuthorized":null,"errorMessage":"validate detected
> invalid orgUnit name [non-existing-ou] adding user with userId
> [test1]","entity":null,"entities":null,"values":null,"valueSet":null,"session":null}
> {code}
> I propose to add a new {{httpStatusCode}} field to FortResponse class which
> can be set appropriately and modify/add the CXF interceptor to change the
> outgoing response's status accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-258) Updating the way FortResponse is served
[
https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-258.
---
Resolution: Fixed
> Updating the way FortResponse is served
> ---
>
> Key: FC-258
> URL: https://issues.apache.org/jira/browse/FC-258
> Project: FORTRESS
> Issue Type: Bug
>Reporter: Kiran Ayyagari
>Assignee: Kiran Ayyagari
>Priority: Major
>
> The FortResponse instance created as a result of operation exception is still
> sent to the client with a HTTP status code of "200 OK" forcing clients to
> rely on the {{errorCode}} field to figure out the actual status of the
> operation.
> For example when the below request is sent to a stock Fortress REST service
> {code}
> curl -POST http://localhost:7070/fortress-rest/userAdd --header
> "Content-Type: application/json" --header "Accept: application/json" --header
> "Authorization: Basic dGVzdDpwYXNzd29yZA==" -v -d '{ "entity": { "fqcn":
> "org.apache.directory.fortress.core.model.User", "userId": "test1", "ou":
> "non-existing-ou" }, "contextId": "HOME" }'
> {code}
> the below success response is received though the request was failed due to a
> validation error which ideally should have been responded with a "400 bad
> request" error.
> {code}
> * Trying ::1...
> * TCP_NODELAY set
> * Connected to localhost (::1) port 7070 (#0)
> > POST /fortress-rest/userAdd HTTP/1.1
> > Host: localhost:7070
> > User-Agent: curl/7.54.0
> > Content-Type: application/json
> > Accept: application/json
> > Authorization: Basic dGVzdDpwYXNzd29yZA==
> > Content-Length: 138
> >
> * upload completely sent off: 138 out of 138 bytes
> < HTTP/1.1 200
> < Date: Fri, 16 Nov 2018 15:05:04 GMT
> < Content-Type: application/json
> < Transfer-Encoding: chunked
> <
> * Connection #0 to host localhost left intact
> {"errorCode":1035,"isAuthorized":null,"errorMessage":"validate detected
> invalid orgUnit name [non-existing-ou] adding user with userId
> [test1]","entity":null,"entities":null,"values":null,"valueSet":null,"session":null}
> {code}
> I propose to add a new {{httpStatusCode}} field to FortResponse class which
> can be set appropriately and modify/add the CXF interceptor to change the
> outgoing response's status accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (FC-295) Move/Improve RBAC Accelerator Client
Shawn McKinney created FC-295: - Summary: Move/Improve RBAC Accelerator Client Key: FC-295 URL: https://issues.apache.org/jira/browse/FC-295 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.5 Reporter: Shawn McKinney Fix For: 3.0.0-RC1 The RBAC Accelerator client code is currently is inoperable. It needs to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-238) Migrate to LDAP API 2.0
[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-238. --- Resolution: Fixed > Migrate to LDAP API 2.0 > --- > > Key: FC-238 > URL: https://issues.apache.org/jira/browse/FC-238 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > The code compiles, but gets NPE when fortress tries to open a pool to the > server > ** > Steps to recreate. > # Get fortress env, checkout latest, follow the steps in DOCKER README to > get either openldap or apacheds server up. > # You may skip the junit tests, do the data loads, i.e. mvn test -Pload.file= > ## in order to verify the env is running correctly run this test: > ### mvn test -Pconsole <-– should be no errors > # Now checkout the code that is using ldap api 2.0.0 > ## git checkout 7fdd12f6aef06c43817c6f6a71baeb67f9e19000 > # connect with fortress console: > ## mvn test -Pconsole > Get the error: > > 2018-07-30 11:25:054 INFO CodecFactoryUtil:404 - > MSG_06002_REGISTERED_INTERMEDIATE_FACTORY (1.3.6.1.4.1.4203.1.9.1.4) > [WARNING] > org.apache.directory.fortress.core.CfgRuntimeException: Exception caught > initializing Admin Pool: java.lang.NullPointerException, errCode=135 > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:191) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.(LdapConnectionProvider.java:116) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.getInstance(LdapConnectionProvider.java:103) > at > org.apache.directory.fortress.core.ldap.LdapDataProvider.closeAdminConnection(LdapDataProvider.java:1215) > at > org.apache.directory.fortress.core.impl.ConfigDAO.getConfig(ConfigDAO.java:327) > at org.apache.directory.fortress.core.impl.ConfigP.read(ConfigP.java:175) > at > org.apache.directory.fortress.core.impl.ConfigMgrImpl.read(ConfigMgrImpl.java:102) > at > org.apache.directory.fortress.core.util.Config.getRemoteConfig(Config.java:377) > at > org.apache.directory.fortress.core.util.Config.loadRemoteConfig(Config.java:655) > at > org.apache.directory.fortress.core.util.Config.getInstance(Config.java:101) > at > org.apache.directory.fortress.core.AdminMgrFactory.createInstance(AdminMgrFactory.java:68) > at > org.apache.directory.fortress.core.AdminMgrConsole.(AdminMgrConsole.java:74) > at > org.apache.directory.fortress.core.ProcessMenuCommand.(ProcessMenuCommand.java:38) > at > org.apache.directory.fortress.core.FortressConsole.main(FortressConsole.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.loadControls(StandaloneLdapApiService.java:313) > at > org.apache.directory.api.ldap.codec.standalone.StandaloneLdapApiService.(StandaloneLdapApiService.java:174) > at > org.apache.directory.fortress.core.ldap.LdapConnectionProvider.init(LdapConnectionProvider.java:180) > ... 19 more > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-289) [fortress-web] get log4j2 working
[ https://issues.apache.org/jira/browse/FC-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-289. --- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 Resolution: Fixed > [fortress-web] get log4j2 working > - > > Key: FC-289 > URL: https://issues.apache.org/jira/browse/FC-289 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > Loggers not working with log4j2, this in logs: > > ``` > log4j:WARN No appenders could be found for logger > (org.apache.directory.fortress.web.model.UserListModel). > log4j:WARN Please initialize the log4j system properly. > ``` > > Change this: > > ``` > import org.apache.log4j.Logger; > private static final Logger LOG = Logger.getLogger( ... ); > ``` > to > ``` > import org.slf4j.Logger; > import org.slf4j.LoggerFactory; > private static final Logger LOG = LoggerFactory.getLogger( ... ); > ``` > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (FC-286) To Apache Log4j 2
[ https://issues.apache.org/jira/browse/FC-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-286. --- Fix Version/s: (was: 3.0.0-RC1) 2.0.6 Resolution: Fixed > To Apache Log4j 2 > - > > Key: FC-286 > URL: https://issues.apache.org/jira/browse/FC-286 > Project: FORTRESS > Issue Type: Improvement >Affects Versions: 2.0.5 >Reporter: Shawn McKinney >Assignee: Shawn McKinney >Priority: Major > Fix For: 2.0.6 > > > Upgrade to Log4j 2, due to vulnerabilities such as: > [https://github.com/advisories/GHSA-2qrg-x229-3v8q] > > in the old libs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-285) [fortress-core]Infinite loop in property interpolation of ${min.log.conn}: min.log.conn
[
https://issues.apache.org/jira/browse/FC-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-285:
--
Fix Version/s: (was: 3.0.0-RC1)
2.0.6
> [fortress-core]Infinite loop in property interpolation of ${min.log.conn}:
> min.log.conn
>
>
> Key: FC-285
> URL: https://issues.apache.org/jira/browse/FC-285
> Project: FORTRESS
> Issue Type: Bug
>Affects Versions: 2.0.5
>Reporter: Shawn McKinney
>Assignee: Shawn McKinney
>Priority: Major
> Fix For: 2.0.6
>
>
> Using the same name for interpolation variable as the property itself creates
> an infinite loop if the property is not set.
>
> rename this:
> lmin.log.conn=1
> max.log.conn=3
> to:
> *log.min.conn=1*
> *log.max.conn=3*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
