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 now and then. Which

Re: Google Analytics / GDPR

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

[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

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 > the

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: > > * 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 allow

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

[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.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.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.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&L files Good catch. Checke

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 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

[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

[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 role-bas

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

what 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 anno

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] https://issues.apache.org/jira/browse/

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 fo

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?

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 c

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 been

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). St

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 ou

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

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: https://github.com/apache/directory-fortress-core/blob/master/src/docker/openldap-for-apache-fortress-

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: 'Access

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 move

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 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 re-adde

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

[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: [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 M

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: 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, a

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: [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

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 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 in

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,

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

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 > https://svn.apache.

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 >> studio/users-guide/2.0.0.v201809

[ANNOUNCE] Apache Fortress 2.0.2 Released

The Apache Directory Project announces the ninth release of Fortress — 2.0.2. 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 role-based

Re: Anyone going to ApacheCon in Montreal?

> On Sep 13, 2018, at 6:04 AM, Colm O hEigeartaigh wrote: > > > Yes I'll be there as well - hope to see you there! Great! I saw that you’re speaking on Thursday. Pity that I’m leaving on that day. Looks like an interesting talk, hope it’s recorded. Will see you there... —Shawn

Re: Anyone going to ApacheCon in Montreal?

> On Sep 14, 2018, at 3:59 AM, Pierre Smits wrote: > > Unfortunately I can't justify the projected cost against the implied > benefits, so I won't be there (though I pity that much). > > But there are talks that in 2019 there might be an ApacheCon EU event. I am > hoping that will materiali

Re: Anyone going to ApacheCon in Montreal?

> On Sep 14, 2018, at 7:24 AM, Moyer, Steven William wrote: > > I won't be in Montreal but I'm thinking about proposing a talk at the > ApacheCon Roadshow in DC ... is anyone else planning to talk about > identity-related subjects there? > Haven’t got that far into the future yet Steve. Wi

Re: rm -rf *Decorator ;-)

> On Oct 3, 2018, at 9:12 AM, Emmanuel Lécharny wrote: > > The problem is that the implementation was really a nightmare (and still > is). Anyone who wants to add a new extendedOperation or a nex Control > has to go through many classes and is likely to get lost (I experienced > it last month wh

New Fortress Release 2.0.3

Hello, This is notification of intent to begin working on a new release of fortress 2.0.3, includes enhancements and bug fixes: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012315921%20AND%20fixVersion%20%3D%2012344047%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC Please let me kno

Re: New Fortress Release 2.0.3

But maybe it's too short term before the actual > release :) > > Kind Regards, > Stefan > > > On 10/26/18 5:29 PM, Shawn McKinney wrote: >> Hello, >> >> This is notification of intent to begin working on a new release of fortress >> 2.0.3, include

[VOTE] Apache Fortress 2.0.3 release

Hello, This is an announcement to vote for the next release of Apache Directory Fortress, 2.0.3. Here are the list of bugs and enhancements: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012315921%20AND%20fixVersion%20%3D%2012344047%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC A ta

[VOTE][RESULT] Apache Fortress 2.0.3 release

> I haven't ran the docker test, I haven't installed docker on my (limited) > machine. > > +1 > > On Tue, Nov 6, 2018 at 2:38 PM Shawn McKinney wrote: > >> Hello, >> >> This is an announcement to vote for the next release of Apache Di

[ANNOUNCE] Apache Fortress 2.0.3 Released

The Apache Directory Project announces its tenth release of Fortress! 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 role-based access

Caching in Fortress Core

Many years ago I made a very bad decision that has haunted me ever since — caching. That’s right, short-term gratification (performance) at the expense of long-term satisfaction. The biggest drawback, now things like Fortress REST aren’t running entirely stateless, which prevents running in a

Fortress' New Logo Usage on Project Website

Hi, Recently a new logo was adopted: https://github.com/apache/directory-fortress-core/blob/master/images/ApacheFortressLogo_FINAL_SM.png Comes in variations, w/out text, size, etc. I’d like to start using this on fortress’ website but want to make sure it’s OK, and hopefully obtain some guidan

Re: Caching in Fortress Core

> On Nov 16, 2018, at 4:20 PM, Emmanuel Lecharny wrote: > > Persistent search is definitely an option, I think. Fortress will receive all > the updates coming from the LDAP server, and update the cache accordingly. > Now, that may not be that simple: > * consistency: not such a big deal, as so

Re: Caching in Fortress Core

> On Nov 19, 2018, at 6:37 AM, Shawn McKinney wrote: > > Two, its worth outweighs the value. er, costs more than its worth. signature.asc Description: Message signed with OpenPGP

Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Hello, Currently there are four fortress repos on git-wip-us affected by this change. https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git ht

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann wrote: > > If time allows I'd suggest to follow the voluntary relocation. > > For Fortress, if you consider to merge the 4 repos into one, this would > be a good time now. Just create a new "directory-fortress" repo at > Gitbox [1] and merge the 4

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

> On Dec 9, 2018, at 11:08 AM, Stefan Seelmann wrote: > > On 12/9/18 5:37 PM, Shawn McKinney wrote: >> >> In other words, does this change to combine the four into a single git >> project repo force us to also change the structure (and process) of the >>

Re: Exception Running ApacheDS embedded

> On Dec 12, 2018, at 5:08 AM, Emmanuel Lécharny wrote: > > if you include ApacheDS, it will implicitely include LDAP API, so including > ldap-api-all will be a duplicate, AFAIR. Here, fortress core apacheDS depends are: test, and of course we have compile-time dependency on the api. > > O

Re: [VOTE] - Release Apache Kerby 2.0.0

> On Dec 11, 2018, at 5:49 AM, Colm O hEigeartaigh wrote: > > This is a vote to release Apache Kerby 2.0.0. > +1 Downloaded kerby-all-2.0.0-source-release.zip, validated its signature, built on the OpenJDK Runtime Environment (build 1.8.0_191-b12) / CentOS Linux release 7.5.1804 -- passed a

Re: Exception Running ApacheDS embedded

xception( resourceName, > resourceDescription ); > } > URL result = resources.nextElement(); > if ( resources.hasMoreElements() ) { > log.debug( "found more than one copy of " + resourceName + " > using first one" ); > } >

Re: Welcome to Lothar !

Glad to have you onboard Lothar! Shawn > On Dec 17, 2018, at 7:40 AM, Lucas Theisen wrote: > > Welcome Lothar! > > On Mon, Dec 17, 2018, 1:29 AM Kiran Ayyagari Welcome Lothar!, been a while since we last welcomed one :) > > On Mon, Dec 17, 2018 at 11:47 AM Emmanuel Lécharny > wrote: > I'm

Re: Exception Running ApacheDS embedded

gt; project. However, even if i missed something in the README, the project > itself is a fully working example that demonstrates how i test my password > policy. It should not be all that difficult to adapt to your use case. Hope > it helps! > > Lucas > > On Fri, Dec 14,

Re: Exception Running ApacheDS embedded

> On Dec 19, 2018, at 9:39 AM, Emmanuel Lécharny wrote: > > sorry for the delayed response. > > For some reason, ldap-api-all is being loaded while it should not. I have > tried to get rid of it, but it's also present in many dependencies (as a > third party), so it's quite painful. > > One

Re: Welcome to Lothar !

> > On Dec 19, 2018, at 4:16 PM, Lothar Haeger > wrote: > > I've already managed to link my shiny brand new Apache ID ("lhaeger") to my > GitHub account, so a first question would be: what - if any - are the pros and > cons of using gitbox vs github? Good question. I’ll probably use gitbox,

Fwd: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Hello, As directed in the message below, we must migrate out four git repos from the existing git-wip-us.apache.org to gitbox.apache.org . Specifically the repos include: directory-fortress-core directory-fortress-realm directory-fo

Re: Mavibot status?

Fortress core also uses this lib, have just upgraded, release in a couple of weeks. > On Jan 4, 2019, at 5:40 AM, Emmanuel Lécharny wrote: > > Hi Colm, > > I doubt Mavibot is going to be hit by this CVE, but we can upgrade and cut a > release if needed. > > > Give me a bit of time to double

Re: [VOTE] Require Java 8 for Apache Directory projects

> On Jan 5, 2019, at 1:06 AM, Emmanuel Lécharny wrote: > > So I suggest we drop Java 7 as the base version for our project, and switch > to Java 8 (which is also EOLed, ftr). > > > [ ] +1 : Only support Java 8 from now on > > [ ] +/- 0 : I don't mind > > [ ] -1 : Keep support for Java 7 +

Re: [VOTE] - Release Apache Kerby 2.0.0 - take II

+1 [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 5:25.228s [INFO] Finished at: Fri Jan 11 15:52:47 UTC 2019 [INFO] Final Memory: 93M/419M [INFO] [stude

Re: Jenkinsfile and pipeline

> > On Jan 21, 2019, at 1:06 PM, Stefan Seelmann wrote: > > Let me know what you think or if you have objections or questions. > Otherwise I'd continue with more Jenkinsfiles :) +1, sounds like a great idea to me. Is this something we can divide and conquer? I’ve never done this, but it’s so

Opportunity to attend and speak ApacheCon

Hello, Later this year are two ApacheCon’s, one in Vegas (Sep 9-13), the other Berlin (Oct 22-24). First, if you are a committer on any project, There’s a deep discount for attendance. Second, if you’re selected to speak the fee is waived. Sometimes, speakers are provided travel stipend as w

Re: [VOTE] Release Apache LDAP API 1.0.3

> On Apr 17, 2019, at 6:29 AM, Emmanuel Lécharny wrote: > > Please cast your votes: > [ ] +1 Release Apache LDAP API 1.0.3 > [ ] 0 abstain > [ ] -1 Do not release Apache LDAP API 1.0.3 +1, download source bundle, built, passed all API tests. Next tested with fortress Core and apacheDS (ldap:3

Working on Fortress Docker Images / Builds / Jenkins tests

Hi, The docker images used by fortress to test openldap and apacheDS have been recently updated to support a minor change in the data schema, to support additional configuration params. https://hub.docker.com/r/apachedirectory/openldap-for-apache-fortress-tests/ https://hub.docker.com/r/apache

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 17, 2019, at 2:31 PM, Shawn McKinney wrote: > > That is to say, that running the test on a local VM finishes in < 10 minutes, > while in a Jenkins pipeline much longer, > 1 hour. It feels like the tests are running inside a VM that’s underpowered. The adds, updat

Re: Opportunity to attend and speak ApacheCon

> On Apr 18, 2019, at 3:40 PM, Smith, Shawn Eion wrote: > > Hey Arkanshawn, > > Hope all's well. I talked to folks here and we would be willing to put > together a talk on Scimple. Any advice for this particular audience would be > greatly appreciated. > > Pennsylshawn Hey Pennsylshawn,

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 18, 2019, at 3:49 PM, Stefan Seelmann wrote: > > Yes, the Jenkins machines are rather slow, I agree. > > There is a bit info (memory and disk) in the Jenkins wiki [1], our jobs > use the "ubuntu" label. For further info we need ask builds@a.o list. > > What's also possible, if you de

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 21, 2019, at 2:22 PM, Stefan Seelmann wrote: > > Some more observations when I run the ApacheDS pipeline: > > Some builds finish in only 15-20 minutes, those run on host ubuntu-eu2 > or ubuntu-eu3. However builds on one of the H2x or H3x nodes take 40-60 > minutes. Hi Stefan, Notice

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 23, 2019, at 9:02 AM, Shawn McKinney wrote: > > Looking at the job config, can we try something like this? > > "Restrict where this project can be run” > > ubuntu && !(H2% || H3%) > > That is are wildcards supported? Couldn’t figure it out b

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 23, 2019, at 12:21 PM, Stefan Seelmann wrote: > > I got an error because between H33 and H34 there is only on |. after > fixing it saved. maybe try again? > > To get Jenkins access I only know [1], you can check yourself if you are > in that group ;) After correcting was able to save

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 23, 2019, at 12:28 PM, Shawn McKinney wrote: > > Now running the job and it seems to be doing the right thing. Stay tuned, > will report back here where this ends up. Hello, A few more days, many successful test runs and we can say this issue has been resolved. A

Latest Fortress Downloads 403

Noticed today that all of the links on the latest fortress downloads, sources and binaries, are 403’s. Scratching my head wondering what’s changed / gone wrong. Anyone have ideas before I start digging? —Shawn

Re: Latest Fortress Downloads 403

> On May 1, 2019, at 8:59 AM, Emmanuel Lécharny wrote: > > No idea what happens, but I restored the packages. It will take a bit for > mirrors to see them. Thanks Emmanuel. We’ve seen stuff like this happen before. Once it was javadoc going missing. Perhaps an SVN update on the dist re

Re: Jira at Apache

> On May 1, 2019, at 7:45 AM, Moyer, Steven William wrote: > > Moving SCIMple's issue tracking to Github also seems to be more in line with > Apache's five-year strategic plan - item three under the "ASF Services - > Infrastructure" heading states "Encourage more use of externally provided >

Re: Jira at Apache

> On May 1, 2019, at 9:20 AM, Shawn McKinney wrote: > > Granted many people are big fans of JIRA. But it works OK and that’s where > one would expect to find the projects issues. Err, many people are NOT big fans...

Re: Latest Fortress Downloads 403

> On May 1, 2019, at 9:40 AM, Emmanuel Lécharny wrote: > > I have somehow cleaned up dist a couple of days ago, and I have removed 2.0.3 > by mistake : > > $ history | grep 2.0.3 > > svn del 2.0.0 2.0.1 2.0.0-RC1 2.0.0-RC2 2.0.3 > > > The thing is that we should only keep the latest versio

Re: Jira at Apache

> On May 1, 2019, at 9:39 AM, Moyer, Steven William wrote: > > To be clear, I'm not for or against Jira - there are pluses and minuses to > both Jira and Github issues. I'm just trying to get in step with the > long-term plan and perhaps more importantly, not merge the issues from the > two

Re: [VOTE] Release Apache LDAP API 2.0.0.AM3

+1, built from source, verified sha512 sigs. —Shawn > On May 12, 2019, at 1:02 AM, Emmanuel Lécharny wrote: > > Hi all, > > this is a vote for the release of Apache LDAP API 2.0.0.AM3, the third > milestone toward a 2.0 > > It contains many fixes (37) and is needed to be able to release Apac

Re: [VOTE] Release Apache LDAP API 2.0.0.AM4

+1. Downloaded distros, built from source, checked the sha512 sigs. —Shawn > On Jun 6, 2019, at 7:16 AM, Colm O hEigeartaigh wrote: > > +1. > > Colm. > > On Wed, Jun 5, 2019 at 9:56 PM Emmanuel Lécharny wrote: > Hi all, > > this is a vote for the release of Apache LDAP API 2.0.0.AM4, the f

Supporting Java9++

Hello, An assertion about Java9 support… Directory projects should support Java9++ but not require it. The adding part is pretty easy. Update the pom, change the compiler plugin, add missing dependencies for JAXB, … The not requiring is perhaps the tricky part. What is the best way to allow

Re: Supporting Java9++

>> backward compatibility with any of the dependencies you update. >> I do something similar at my day job, and IIRC Spring does this too. >> >> >> On Mon, Jun 17, 2019 at 10:37 AM Shawn McKinney >> wrote: >> >>> Hello, >>> >>>

Announcing LDAPCon 2019!

> From https://ldapcon.org/2019/ It's high time we shared the news: the 7th Conference on LDAP, Directory Services and Identity Management will take place November 4-6th at the Holiday Inn in Sofia, Bulgaria. November 4th is set aside for workshops, November 5th and 6th will be the regular sess

Re: Announcing LDAPCon 2019!

are welcome and considered equals making it one of the most valuable and unique experiences for technology enthusiasts. —Shawn > On Jul 5, 2019, at 8:04 AM, Shawn McKinney wrote: > >> From https://ldapcon.org/2019/ > > It's high time we shared the news: the 7th Confer

Re: Can help me some demo code about Delegation Control in AD in ldap api

Hello, > On Sep 12, 2019, at 1:41 AM, Chung Tran wrote: > > - i found about open source project like this : > https://www.programcreek.com/java-api-examples/?code=apache%2Fdirectory-fortress-enmasse%2Fdirectory-fortress-enmasse-master%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fdirectory%2Ffortress%2F

Re: Can help me some demo code about Delegation Control in AD in ldap api

> On Sep 12, 2019, at 7:49 AM, Shawn McKinney wrote: > > Fortress provides administrative delegation using the ARBAC02 model. I’m > sure you could do some searching to learn more if you have interest. Here’s a primer on the topic. Wish I had something to share with you th

Re: Can help me some demo code about Delegation Control in AD in ldap api

> On Sep 12, 2019, at 8:44 AM, Shawn McKinney wrote: > > Also you asked about pw policies: > > https://iamfortress.net/2015/06/11/what-are-password-policies/ > > NOt so difficult of a topic as delegation. Should be easier to find some > samples. > > Here’s

Re: Can help me some demo code about Delegation Control in AD in ldap api

And finally, the project doc page on pw policies: https://directory.apache.org/apacheds/advanced-ug/4.3-password-policy.html > On Sep 12, 2019, at 8:45 AM, Shawn McKinney wrote: > > >> On Sep 12, 2019, at 8:44 AM, Shawn McKinney wrote: >> >> Also you asked abou

Re: New releases?

Sounds good, go for it. (+1) — Shawn > On Nov 5, 2019, at 10:03 AM, Emmanuel Lécharny wrote: > > I can start a new release of LDAP API today. > > > On 04/11/2019 11:54, Colm O hEigeartaigh wrote: >> Where do we stand on new releases? There have been quite a few fixes in the >> API that coul

Re: [VOTE] Release Apache LDAP API 2.0.0

+1, Java 11 Nice to have the release train started back up. — Shawn > On Nov 7, 2019, at 3:23 PM, Radovan Semancik > wrote: > > +1 > > OpenJDK 11.0.4. Tested with AD and OpenDJ. > > -- > Radovan Semancik > Software Architect > evolveum.com > > > > On 11/6/19 3:09 PM, Emmanuel Lécharny w

Another Fortress release

Hello, Somehow 2019 is almost past and yet we have not had a release of fortress yet. There were a couple of things that have been in the hopper that I’ve been waiting on. Upgrade to 2.0 ldap api and to a lesser extent, release of the new gui that Kiran worked on. However that work has stalle

  1   2   3   4   5   6   7   8   9   10   >