Re: Error deploying to staging changes to production website

> On Sep 12, 2018, at 2:27 PM, Stefan Seelmann wrote: >> Ah, wait. Maybe the reason is that in extpaths.txt the new docs I put >> into a subfolder, but the parent is already defined in extpaths. I'll >> remove the child... >> >> # Studio >> studio/users-guide >>

Re: Error deploying to staging changes to production website

> On Sep 12, 2018, at 2:09 PM, Stefan Seelmann wrote: > > Hm, I pushed the Studio user's guide for the current in-vote release > already to the production website, but also added it to > content/extpaths.txt in trunk (and thus staging) > > On staging it's there: > svn cat >

Error deploying to staging changes to production website

Hi all, running through the checklist on fortress release, deploying to production website, changes made to staging. I’m getting this error and unsure how to proceed: production/directory/content/studio/users-guide/2.0.0.v20180908-M14' already exists does this ring a bell? Thanks — Shawn

Result, was: [VOTE] Apache Fortress 2.0.2 release

Hi, I’m closing this vote, it was successful. We received 4 binding +1 votes: Emmanuel, Stefan, Kiran and I. There were a few items caught during the voting. The signatures was fixed (-.md5, sha1, +sha256, sha512), per Emmanuel’s instructions. The other items related to installation docs,

Re: [VOTE] Apache Fortress 2.0.2 release

> On Sep 11, 2018, at 12:43 PM, Emmanuel Lécharny wrote: > >>> >>> On Sep 11, 2018, at 5:43 AM, Emmanuel Lécharny wrote: >>> , and on MacOSC, tomcat is not >>> excatly installed as described >>> (/usr/local/tomcat8/apache-tomcat-8.0.30/... instead of >>> /usr/local/tomcat8/... as specified

Re: [VOTE] Apache Fortress 2.0.2 release

> On Sep 11, 2018, at 12:24 PM, Lothar Haeger > wrote: > > Shawn McKinney wrote: > >> mv apache-tomcat-8.0.30 /usr/local/tomcat8 >> >> Not sure why on a Mac (in Bash) the mv command appends distro name to the >> path and not in Linux. >

Re: [VOTE] Apache Fortress 2.0.2 release

> On Sep 11, 2018, at 5:43 AM, Emmanuel Lécharny wrote: > > A few remarks : > > - signatures on dist should not supply a SHA1 signature (neither a MD5), > SHA256 or/and SHA512 should be provided bseside a .asc file. You can > easily add the sha256/512 signatures to the existing dist directory

Anyone going to ApacheCon in Montreal?

Hello, Got accepted to fill-in for upcoming ACNA talk in Montreal, wondering if anyone else will be there. Let me know, if you’re there, and we’ll grab a burger and/or some beer. --Shawn

Re: ApacheDS support

Hello, there’s also this page with a couple of options. https://directory.apache.org/commercial-support.html --Shawn > On Sep 10, 2018, at 8:11 AM, Pierre Smits wrote: > > Moving to the more public ML > > Hi Freddy, > > Thank you for reaching out to the PMC of the Apache Directory project,

[jira] [Created] (FC-244) [fortress-core] builds fail in Java 11

Shawn McKinney created FC-244: - Summary: [fortress-core] builds fail in Java 11 Key: FC-244 URL: https://issues.apache.org/jira/browse/FC-244 Project: FORTRESS Issue Type: Improvement

Re: [VOTE] Apache Fortress 2.0.2 release

> On Sep 10, 2018, at 12:33 AM, Stefan Seelmann wrote: > > > PS: Build of fortress-core with Java 11+ea25 fails because java.xml.bind > is no longer part of JDK Thanks Stefan. Ticket created to track this issue. https://issues.apache.org/jira/browse/FC-244 —Shawn

Re: [VOTE] Apache Directory Studio 2.0.0.v20180908-M14 release

> On Sep 9, 2018, at 11:23 AM, Stefan Seelmann wrote: > > Please cast your vote: > [ ] +1 : release Apache Directory Studio 2.0.0.v20180908-M14 > [ ] ± 0 : I don't care > [ ] -1 : No, don't release Apache Directory Studio 2.0.0.v20180908-M14 +1, built from source here: $ mvn -version Apache

[VOTE] Apache Fortress 2.0.2 release

Hello, This is an announcement to vote for the next release of Apache Directory Fortress. The version, 2.0.2, has a tag created for git: ‘2.0.2’. and the sources may be pulled using git commands: git clone --branch 2.0.2 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git git

Re: Working on dir-fortress-core-docker-openldap-test failures in jenkins

> > On Sep 9, 2018, at 1:04 AM, Stefan Seelmann wrote: > > Cool, thanks. > > I replaced both, the OpenLDAP and ApacheDS one. The OpenLDAP runs stable > now. Very nice. > On Sep 9, 2018, at 1:04 AM, Stefan Seelmann wrote: > > However the test that uses ApacheDS always fails. Either it times

[jira] [Created] (FC-243) [fortress-realm] proxy to use tomcat 9 interface

Shawn McKinney created FC-243: - Summary: [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

Re: Working on dir-fortress-core-docker-openldap-test failures in jenkins

> On Sep 8, 2018, at 2:00 AM, Stefan Seelmann wrote: > > > I wanted to do that now, but now the src/docker and other config folders > are gone, was that on purpose? Negative, was a mistake, on my part. I’ve had some strange effects in my dev VM. Anyway these files/folders have been

[jira] [Resolved] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-240. --- Resolution: Fixed checked in, to test, run:   >mvn install -Powasp > Please add OWASP Depe

[jira] [Comment Edited] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607233#comment-16607233 ] Shawn McKinney edited comment on FC-240 at 9/7/18 3:12 PM: --- Another problem running

[jira] [Commented] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607233#comment-16607233 ] Shawn McKinney commented on FC-240: --- Another problem running the owasp plug-in, requires maven 3.1.  Once I

[jira] [Commented] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607231#comment-16607231 ] Shawn McKinney commented on FC-240: --- For some odd reason, the scanner tags openldap accelerator jars,(api

[jira] [Commented] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607159#comment-16607159 ] Shawn McKinney commented on FC-240: --- Howto:   1. Add new plugin to fortress-core pom.xml

[jira] [Updated] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-240: -- Fix Version/s: 2.0.2 > Please add OWASP Dependency Check to the build (pom.

[jira] [Updated] (FC-237) OrgUnitDAO uses case sensitive operation to determine set membership

[ https://issues.apache.org/jira/browse/FC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-237: -- Fix Version/s: 2.0.2 > OrgUnitDAO uses case sensitive operation to determine set members

[jira] [Resolved] (FC-239) Some additional methods to manage role constraints.

[ https://issues.apache.org/jira/browse/FC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-239. --- Resolution: Fixed Added: AccessMgr Session createSession( User user, List constraints, boolean

[jira] [Resolved] (FC-242) Rename RoleConstraint attribute paSetName to key

[ https://issues.apache.org/jira/browse/FC-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-242. --- Resolution: Fixed Done, passes junit tests. > Rename RoleConstraint attribute paSetName to

[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.2) 2.0.3 > Migrate to LDAP API

[jira] [Resolved] (FC-237) OrgUnitDAO uses case sensitive operation to determine set membership

[ https://issues.apache.org/jira/browse/FC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-237. --- Resolution: Fixed new code fixed the issue: if ( dn.toLowerCase().contains( getRootDn( contextId

Re: [VOTE] Apache LDAP API 2.0.0.AM2

> On Aug 29, 2018, at 1:39 AM, Emmanuel Lécharny wrote: > > > Please cast your votes: > [ ] +1 Release ApacheLDAP API 2.0.0.AM2 > [ ] 0 abstain > [ ] -1 Do not release Apache LDAP API 2.0.0.AM2 > +1, Centos 7, Openjdk 8. Built, tests, success, verified SHA signatures. —Arkanshawn

Re: Working on dir-fortress-core-docker-openldap-test failures in jenkins

> On Aug 28, 2018, at 1:27 PM, Stefan Seelmann wrote: > >> https://builds.apache.org/view/D/view/Directory/job/dir-fortress-core-docker-openldap-test/configure >> >> It doesn't use the run-tests.sh script at all. All the instructions are >> duplicated there. I guess I did that, not a nice

Re: Working on dir-fortress-core-docker-openldap-test failures in jenkins

> On Aug 28, 2018, at 12:17 AM, Stefan Seelmann wrote: > > Please have a look into the Jenkin job configuration: > https://builds.apache.org/view/D/view/Directory/job/dir-fortress-core-docker-openldap-test/configure Ah yes that’s is what I figured. Btw, when I go to that page, I get:

Working on dir-fortress-core-docker-openldap-test failures in jenkins

Howdy, A couple of issues running fortress builds in jenkins on docker images. The openldap one is topic of this post. Specifically, the problem with how the docker script runs: excerpt from:

[jira] [Created] (FC-242) Rename RoleConstraint attribute paSetName to key

Shawn McKinney created FC-242: - Summary: Rename RoleConstraint attribute paSetName to key Key: FC-242 URL: https://issues.apache.org/jira/browse/FC-242 Project: FORTRESS Issue Type: Improvement

[jira] [Commented] (FC-241) Associate Organization Unit with Permission Operation mapping

[ https://issues.apache.org/jira/browse/FC-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590754#comment-16590754 ] Shawn McKinney commented on FC-241: --- This request has been made before. Checkout this ML thread: [http

[jira] [Assigned] (FC-241) Associate Organization Unit with Permission Operation mapping

[ https://issues.apache.org/jira/browse/FC-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-241: - Assignee: Shawn McKinney > Associate Organization Unit with Permission Operation mapp

[jira] [Updated] (FC-239) Some additional methods to manage role constraints.

[ https://issues.apache.org/jira/browse/FC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-239: -- Description: Now that Fortress supports attributes within the activation phase, convenience methods

[jira] [Commented] (FC-239) Some additional methods to manage role constraints.

[ https://issues.apache.org/jira/browse/FC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590371#comment-16590371 ] Shawn McKinney commented on FC-239: --- {color:#00}Adding RoleConstraint type USER:{color} {color:#00

Re: ApacheDS 2.0.0.AM25 ad site update

> On Aug 21, 2018, at 12:38 AM, Emmanuel Lécharny wrote: > > Yes, it's critially important to *always* do a svn update on the site > content before publishing the site, and to check that the extpaths > content refers to the latest versions of all the project. Agreed. > > On Aug 21, 2018, at

Re: ApacheDS 2.0.0.AM25 ad site update

> On Aug 20, 2018, at 5:11 PM, Emmanuel Lécharny wrote: > > This is because the extpaths.txt file does not contain a reference to > fortress 2.0.1: > > ... > > Don't worry, we have all be bitten by this, more than once... (no later > than this week-end for me...) Hi Emmanuel, as it turns

Re: ApacheDS 2.0.0.AM25 ad site update

> On Aug 19, 2018, at 4:29 PM, Emmanuel Lécharny wrote: > > I have successfully pushed the release, and updated the web site. > There is one thing that I can't get working, and I don't understand why: > If you try to get to the 2.0.0/AM25 javadocs, you get the previous > version (2.0.0-M24).

Re: [VOTE] Apache DS 2.0.0.AM25 release

> On Aug 14, 2018, at 4:18 AM, Emmanuel Lecharny wrote: > > This is a major release of ApacheDS. > > It uses the Apache LDAP API 2.00.AM1 release, which itself > brings a lot of improvements and bug fixes > > But the major improvement is the cross-indexes transaction > support that has

Re: OWASP Dependency-Check

> On Aug 6, 2018, at 10:10 AM, Brian Demers wrote: > > I’d suggest executing the plunging from a non-default profile. The configure > that profile to run at release time and CI. That way local builds are still > fast by default. +1, run as part of the release process, like the rat plugin

Re: OWASP Dependency-Check

> On Aug 6, 2018, at 8:20 AM, Smith, Shawn Eion wrote: > > We have it in the Scimple pom if you're looking for an example to play with. > Thanks, that is very helpful. I wondering if this should be part of the project pom.WDYT?

OWASP Dependency-Check

Hello, A new ticket was created, asking us to add OWASP dependency scanning of known vulnerabilities. https://issues.apache.org/jira/browse/FC-240 Which points to the OWASP page describing the tool: https://www.owasp.org/index.php/OWASP_Dependency_Check I am going to investigate usage in

[jira] [Assigned] (FC-240) Please add OWASP Dependency Check to the build (pom.xml)

[ https://issues.apache.org/jira/browse/FC-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-240: - Assignee: Shawn McKinney > Please add OWASP Dependency Check to the build (pom.

[jira] [Created] (FC-239) Some additional methods to manage role constraints.

Shawn McKinney created FC-239: - Summary: Some additional methods to manage role constraints. Key: FC-239 URL: https://issues.apache.org/jira/browse/FC-239 Project: FORTRESS Issue Type

[jira] [Created] (FC-238) Migrate to LDAP API 2.0

Shawn McKinney created FC-238: - Summary: 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

Re: Returned post for annou...@apache.org

> On Jul 24, 2018, at 12:26 AM, Stefan Seelmann wrote: > > Best look at the LDAP API download pages, those was recently updated to > the new rules. See also the Jira that Emmanuel created [1]. And also > remove the md5. > > Kind Regards, > Stefan > > [1]

Fwd: Returned post for annou...@apache.org

others think. Thanks, — Shawn > Begin forwarded message: > > From: Private LIst Moderation > Subject: Re: Returned post for annou...@apache.org > Date: July 21, 2018 at 7:06:58 PM CDT > To: Shawn McKinney > Cc: announce-ow...@apache.org > > Two problems with the announ

[ANNOUNCE] Apache Fortress 2.0.1 Released

The Apache Directory Project announces the eighth release of Fortress — 2.0.1. Apache Fortress is a computer security access management facility written in Java. Other platforms use the Apache Fortress Rest component. Fortress provides a fine-grained authorization security model using

[jira] [Resolved] (FC-236) getMessage() on LDAPExceptions returns empty

[ https://issues.apache.org/jira/browse/FC-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-236. --- Resolution: Fixed changed catch to not use .getMessage() > getMessage() on LDAPExceptions returns em

[Result][VOTE] Apache Fortress 2.0.1 release, Take 2

Calling it with +3 for, Colm, Emmanuel and myself. Stefan’s earlier +1 doesn’t count here (it was on the 1st take), but perhaps provides extra assurances we’re in the good. Thanks for the help, I’ll be finishing up with the needful over the w/e. Shawn > On Jul 18, 2018, at 6:56 AM, Sh

Re: [VOTE] Apache LDAP API 2.0.0-AM1

+1 There are compilation errors when adding as dependency to fortress that I’ll need to work through. I realize this is a major revision but is there some sort of migration guide from 1 to 2? Shawn > On Jul 17, 2018, at 4:49 PM, Stefan Seelmann wrote: > > +1 > > * Verified checksums and

Re: [VOTE] Apache Fortress 2.0.1 release, Take 2

> On Jul 17, 2018, at 11:33 AM, Colm O hEigeartaigh wrote: > > +1. The NOTICE files could be updated to change 2016 to 2018. > Done. And thanks Colm. — Shawn

Re: [VOTE] Apache Fortress 2.0.1 release, Take 2

> On Jul 16, 2018, at 4:12 PM, Emmanuel Lécharny wrote: > > My +1 > > - Tested the sources > - Tested the dist packages > - Checked the signatures (ftr, the > fortress-realm-2.0.1-source-release.zip.asc file is missing) > - Tested against ApacheDS > - Checked the N files Good catch. Checked

[jira] [Updated] (FC-237) OrgUnitDAO uses case sensitive operation to determine set membership

[ https://issues.apache.org/jira/browse/FC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-237: -- Summary: OrgUnitDAO uses case sensitive operation to determine set membership (was: OrgUnitDAO uses case

[jira] [Created] (FC-237) OrgUnitDAO uses case senstive operation to determine set membership

Shawn McKinney created FC-237: - Summary: OrgUnitDAO uses case senstive operation to determine set membership Key: FC-237 URL: https://issues.apache.org/jira/browse/FC-237 Project: FORTRESS

[VOTE] Apache Fortress 2.0.1 release, Take 2

Hello, This is an announcement to vote for the next release of Apache Directory Fortress. The version, 2.0.1, has a tag created for git: ‘2.0.1’. and the sources may be pulled using git commands: git clone --branch 2.0.1 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git git

Re: [VOTE] Apache Fortress 2.0.0 release, Take 2

DOH the wrong version on subject line. Disregard this one, sending out another. Shawn > On Jul 15, 2018, at 3:20 PM, Shawn McKinney wrote: > > Hello, > > This is an announcement to vote for the next release of Apache Directory > Fortress. > > The version, 2.0.1, h

[VOTE] Apache Fortress 2.0.0 release, Take 2

Hello, This is an announcement to vote for the next release of Apache Directory Fortress. The version, 2.0.1, has a tag created for git: ‘2.0.1’. and the sources may be pulled using git commands: git clone --branch 2.0.1 https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git git

Re: [VOTE] Apache Fortress 2.0.1 release

> On Jul 14, 2018, at 10:20 AM, Stefan Seelmann wrote: > > Sure, what else can we do :-/ One thing we can control, what gets uploaded to our download site. I won’t deploy the .md5 artifacts there. Thanks, —Shawn

Re: [VOTE] Apache Fortress 2.0.1 release

> On Jul 9, 2018, at 3:07 PM, Stefan Seelmann wrote: > > * Future releases should not include md5 checksums, please see mail from > Henk with subject "checksum file Release Distribution Policy" and > https://www.apache.org/dev/release-distribution#sigs-and-sums. But > currently it's still

[jira] [Created] (FC-236) getMessage() on LDAPExceptions returns empty

Shawn McKinney created FC-236: - Summary: getMessage() on LDAPExceptions returns empty Key: FC-236 URL: https://issues.apache.org/jira/browse/FC-236 Project: FORTRESS Issue Type: Bug Affects

Cancel, was [VOTE] Apache Fortress 2.0.1 release

Canceling this vote to fix a bug that I found, plus the other problems mentioned before. Will regroup in a few days... Shawn > Begin forwarded message: > > From: Shawn McKinney > Subject: [VOTE] Apache Fortress 2.0.1 release > Date: July 9, 2018 at 9:41:43 AM

Re: [VOTE] Apache Fortress 2.0.1 release

> On Jul 9, 2018, at 3:07 PM, Stefan Seelmann wrote: > > Two findings: > > * Selenium is now included in fortress-web as runtime dependency, I > guess it is only requried as test dependency? License wise that's fine > and not a blocker because it uses Apache License. However it increases >

[VOTE] Apache Fortress 2.0.1 release

Hello, I’m happy to announce that after a year’s worth of work we’ve managed to put together a new release. Just to set expectations, it won’t be another before the next one. There are some interesting items that need out. Yudhi’s High availability being one of them. Also I should mention a

[jira] [Resolved] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-235. --- Resolution: Fixed > Add support for runtime constraints to be placed on activated ro

[jira] [Resolved] (FC-108) Add support for RFC2307 BIS

[ https://issues.apache.org/jira/browse/FC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-108. --- Resolution: Fixed > Add support for RFC2307 BIS > --- > >

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. *Rationale for change* One of the advantages of RBAC is the concept of an activated role

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. *Rationale for change* One of the advantages of RBAC is the concept of an activated role

[jira] [Updated] (FC-214) ApacheDS pw policy defs not multitenant

[ https://issues.apache.org/jira/browse/FC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-214: -- Fix Version/s: (was: 2.0.1) > ApacheDS pw policy defs not multiten

[jira] [Assigned] (FC-102) [fortress-web] fix problems with group page

[ https://issues.apache.org/jira/browse/FC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-102: - Assignee: Shawn McKinney > [fortress-web] fix problems with group p

[jira] [Resolved] (FC-227) Exclude xml-apis from LDAP api

[ https://issues.apache.org/jira/browse/FC-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-227. --- Resolution: Fixed done > Exclude xml-apis from LDAP

[jira] [Resolved] (FC-233) [FORTRESS-REST] Upgrade to Spring 5 and latest CXF

[ https://issues.apache.org/jira/browse/FC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-233. --- Resolution: Fixed > [FORTRESS-REST] Upgrade to Spring 5 and latest

[jira] [Updated] (FC-230) Support Java 9

[ https://issues.apache.org/jira/browse/FC-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-230: -- Fix Version/s: (was: 2.0.1) > Support Java 9 > -- > >

[jira] [Resolved] (FC-234) Close the connection in http get

[ https://issues.apache.org/jira/browse/FC-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-234. --- Resolution: Fixed > Close the connection in http

[jira] [Resolved] (FC-226) ehcache masking security exceptions

[ https://issues.apache.org/jira/browse/FC-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-226. --- Resolution: Fixed done > ehcache masking security excepti

[jira] [Updated] (FC-218) Test case for delete role and memberships

[ https://issues.apache.org/jira/browse/FC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-218: -- Fix Version/s: (was: 2.0.1) > Test case for delete role and membersh

[jira] [Updated] (FC-102) [fortress-web] fix problems with group page

[ https://issues.apache.org/jira/browse/FC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-102: -- Fix Version/s: 2.0.1 > [fortress-web] fix problems with group p

[jira] [Updated] (FC-205) implement PropertyMgrRestImpl

[ https://issues.apache.org/jira/browse/FC-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-205: -- Fix Version/s: (was: 2.0.1) > implement PropertyMgrRestI

[jira] [Updated] (FC-28) The safeText method is probably not useful, and can be faster

[ https://issues.apache.org/jira/browse/FC-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-28: - Fix Version/s: (was: 2.0.1) > The safeText method is probably not useful, and can be fas

[jira] [Updated] (FC-102) [fortress-web] fix problems with group page

[ https://issues.apache.org/jira/browse/FC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-102: -- Fix Version/s: (was: 2.0.1) > [fortress-web] fix problems with group p

[jira] [Updated] (FC-175) [ fortress-web ] Add png file for detail panel controls

[ https://issues.apache.org/jira/browse/FC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-175: -- Fix Version/s: (was: 2.0.1) > [ fortress-web ] Add png file for detail panel contr

[jira] [Updated] (FC-26) Make it possible to programatically configure Fortress

[ https://issues.apache.org/jira/browse/FC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-26: - Fix Version/s: (was: 2.0.1) > Make it possible to programatically configure Fortr

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. *Rationale for change* One of the advantages of RBAC is the concept of an activated role

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. Rationale for change One of the advantages of RBAC is the concept of an activated role

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. Rationale for change One of the advantages of RBAC is the concept of an activated role

[jira] [Updated] (FC-235) Add support for runtime constraints to be placed on activated roles

[ https://issues.apache.org/jira/browse/FC-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-235: -- Description: h3. Rationale for change One of the advantages of RBAC is the concept of an activated role

[jira] [Created] (FC-235) Add support for runtime constraints to be placed on activated roles

Shawn McKinney created FC-235: - Summary: Add support for runtime constraints to be placed on activated roles Key: FC-235 URL: https://issues.apache.org/jira/browse/FC-235 Project: FORTRESS

[jira] [Created] (FC-234) Close the connection in http get

Shawn McKinney created FC-234: - Summary: Close the connection in http get Key: FC-234 URL: https://issues.apache.org/jira/browse/FC-234 Project: FORTRESS Issue Type: Improvement Affects

[jira] [Updated] (FC-233) [FORTRESS-REST] Upgrade to Spring 5 and latest CXF

[ https://issues.apache.org/jira/browse/FC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-233: -- Summary: [FORTRESS-REST] Upgrade to Spring 5 and latest CXF (was: [FORTRESS-REALM] Upgrade to Spring 5

[jira] [Created] (FC-233) [FORTRESS-REALM] Upgrade to Spring 5 and latest CXF

Shawn McKinney created FC-233: - Summary: [FORTRESS-REALM] Upgrade to Spring 5 and latest CXF Key: FC-233 URL: https://issues.apache.org/jira/browse/FC-233 Project: FORTRESS Issue Type

[jira] [Assigned] (FC-108) Add support for RFC2307 BIS

[ https://issues.apache.org/jira/browse/FC-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-108: - Assignee: Shawn McKinney Affects Version/s: (was: 1.0.0-RC42

Re: Google Analytics / GDPR

> On May 23, 2018, at 6:59 AM, Shawn McKinney <smckin...@apache.org> wrote: > > Perhaps there’s another way to gather those stats. … without google analytics.

Re: Google Analytics / GDPR

> On May 22, 2018, at 5:00 PM, Emmanuel Lécharny wrote: > >> Kind Regards, >> Stefan >> >> PS: I don't even know who has access to the GA statistics, I don't want >> to have access anyway. > > I have, but I don't use it frequently. > > We can get rid of it. I look every

[jira] [Resolved] (FC-232) [fortress-web] to Spring 5 and Wicket 7.9

[ https://issues.apache.org/jira/browse/FC-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-232. --- Resolution: Fixed > [fortress-web] to Spring 5 and Wicket

[jira] [Closed] (FC-232) [fortress-web] to Spring 5 and Wicket 7.9

[ https://issues.apache.org/jira/browse/FC-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-232. - > [fortress-web] to Spring 5 and Wicket 7.9 > - > >

[jira] [Created] (FC-232) [fortress-web] to Spring 5 and Wicket 7.9

Shawn McKinney created FC-232: - Summary: [fortress-web] to Spring 5 and Wicket 7.9 Key: FC-232 URL: https://issues.apache.org/jira/browse/FC-232 Project: FORTRESS Issue Type: Improvement

Re: ApacheDS vs OpenDJ testing?

> On Nov 29, 2017, at 9:37 AM, Ludovic Poitou wrote: > > Btw, afaik, all of the tests of servers outside OpenLDAP were done without > any specific tuning. And for DJ it meant that it was running with a 2GB JVM > and almost no cache. > How about we rerun the

[jira] [Resolved] (FC-231) DAO's should be package private

[ https://issues.apache.org/jira/browse/FC-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-231. --- Resolution: Fixed > DAO's should be package priv

[jira] [Created] (FC-231) DAO's should be package private

Shawn McKinney created FC-231: - Summary: DAO's should be package private Key: FC-231 URL: https://issues.apache.org/jira/browse/FC-231 Project: FORTRESS Issue Type: Improvement Affects

<    1   2   3   4   5   6   7   8   9   10   >