Re: [VOTE] Apache DS 2.0.0.AM25 release

[Ludovic Poitou]

This is typical on Windows, if the file hasn’t been closed and released by
a process… Could be a sign of a bug, or not !

My 2 cents.

Ludo

—
Ludovic Poitou
http://ludopoitou.com

On 16 August 2018 at 06:50:20, Emmanuel Lécharny (elecha...@gmail.com)
wrote:

Hi Lucas,

Yes, Windows is having hard time deleting transient files. This is
visible on jenkins.

Not sure we can do anythig regarding this problem, to me it seems that
there is some kind of temporary lock put of those files, and the
deletion just fails...

Le 16/08/2018 à 06:30, Lucas Theisen a écrit :
> +1
>
> However, test fail on Windows during attempts to delete test files. Not
> sure if that is much of a concern...
>
> [ERROR] Errors:
> [ERROR] JdbmIndexTest.cleanup:127 ▒ IO ERR_17010_UNABLE_DELETE_FILE
> Unable to delete f...
> [ERROR] JdbmRdnIndexTest.cleanup:128 ▒ IO ERR_17010_UNABLE_DELETE_FILE
> Unable to delet...
> [INFO]
> [ERROR] Tests run: 124, Failures: 0, Errors: 2, Skipped: 0
>
>
>
> On Aug 15, 2018 4:44 PM, "Emmanuel Lécharny"  wrote:
>
>
>
> Le 15/08/2018 à 21:01, Stefan Seelmann a écrit :
>> +1
>>
>> * Verified checksums and signatures
>> * Built source on Linux with OpenJDK 8 and 11-ea25
>> * Run installer tests:
>> * bin, tar.gz and deb on Debian 9 With OpenJDK 8 and 11-ea24
>> * rpm on Fedora 21 (very old!) with Java 8
>>
>> Note: when starting the server there is output like this:
>> [18:19:00] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
>> ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
>> handle NameAndOptionalUID normalization with obje...
>
> Yes, this should be a warning.
>
> What happens is that the server will load all the schemas, recursively,
> and for each schema, the AT, OC, etc Some of them are loaded before
> the parts they depend on. Each of the attributeTypes and Object classes
> are checked against the registries, and if they don't exist, such an
> error is produced. Then a workaround is applied:
>
> ...
> entry.addAttribute( attributeType, attributeValue ); //
> Here, we will get an exception
> }
> catch ( Exception e )
> {
> // The attribute does not exist already, create a fake one
> if ( ( schemaManager != null ) && schemaManager.isRelaxed() )
> // Here, we create a fake object waiting for the real one to be loaded
>
> Later on, when all the schemas has finally been loaded, all those
> temporary objects are discarded, and a global check is done, which means
> if there is some missing AT, OC or anything else, and error will be
> produced.
>
> Typically, here, an attributeType's super attribute is not yet loaded in
> the registry (apacheDnsDomainName):
>
> version: 1
> dn:
>
m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
> m-singlevalue: TRUE
> m-obsolete: FALSE
> m-description: The domain name of the name server that was the primary
> source of data for this zone
> m-usage: USER_APPLICATIONS
> creatorsname: uid=admin,ou=system
> m-collective: FALSE
> m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
> m-supattributetype: apacheDnsDomainName
> m-nousermodification: FALSE
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-name: apacheDnsSoaMName
> m-equality: caseIgnoreIA5Match
>
> because attribute files are loaded in an order that is not the one we
> can guaranty. That would be another story if the schema elements were
> not in a distinct file for each one of them.
>
> I agree there is room for improvement here, typically not storing each
> AT, OC, etc in a separated file, but as a whole in a .schema file, as
> it's done in OpenLDAP. OTOH, that would make the schema update way more
> complex, as we would have to modify the schema file and create a new one
> for each modification, while the way we work allows us to simply update
> one single fle when we modify the schema.
>
> It's a implementation choice.
>
> Ideally speaking, we should mute the logs in this case, or make it a
> warning, not a error.
>
>
>

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Emmanuel Lécharny]

Hi Lucas,

Yes, Windows is having hard time deleting transient files. This is
visible on jenkins.

Not sure we can do anythig regarding this problem, to me it seems that
there is some kind of temporary lock put of those files, and the
deletion just fails...

Le 16/08/2018 à 06:30, Lucas Theisen a écrit :
> +1
> 
> However, test fail on Windows during attempts to delete test files.  Not
> sure if that is much of a concern...
> 
> [ERROR] Errors:
> [ERROR]   JdbmIndexTest.cleanup:127 ▒ IO ERR_17010_UNABLE_DELETE_FILE
> Unable to delete f...
> [ERROR]   JdbmRdnIndexTest.cleanup:128 ▒ IO ERR_17010_UNABLE_DELETE_FILE
> Unable to delet...
> [INFO]
> [ERROR] Tests run: 124, Failures: 0, Errors: 2, Skipped: 0
> 
> 
> 
> On Aug 15, 2018 4:44 PM, "Emmanuel Lécharny"  wrote:
> 
> 
> 
> Le 15/08/2018 à 21:01, Stefan Seelmann a écrit :
>> +1
>>
>> * Verified checksums and signatures
>> * Built source on Linux with OpenJDK 8 and 11-ea25
>> * Run installer tests:
>> * bin, tar.gz and deb on Debian 9 With OpenJDK 8 and 11-ea24
>> * rpm on Fedora 21 (very old!) with Java 8
>>
>> Note: when starting the server there is output like this:
>> [18:19:00] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
>> ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
>> handle NameAndOptionalUID normalization with obje...
> 
> Yes, this should be a warning.
> 
> What happens is that the server will load all the schemas, recursively,
> and for each schema, the AT, OC, etc Some of them are loaded before
> the parts they depend on. Each of the attributeTypes and Object classes
> are checked against the registries, and if they don't exist, such an
> error is produced. Then a workaround is applied:
> 
> ...
> entry.addAttribute( attributeType, attributeValue ); //
> Here, we will get an exception
> }
> catch ( Exception e )
> {
> // The attribute does not exist already, create a fake one
> if ( ( schemaManager != null ) && schemaManager.isRelaxed() )
> // Here, we create a fake object waiting for the real one to be loaded
> 
> Later on, when all the schemas has finally been loaded, all those
> temporary objects are discarded, and a global check is done, which means
> if there is some missing AT, OC or anything else, and error will be
> produced.
> 
> Typically, here, an attributeType's super attribute is not yet loaded in
> the registry (apacheDnsDomainName):
> 
> version: 1
> dn:
> m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
> m-singlevalue: TRUE
> m-obsolete: FALSE
> m-description: The domain name of the name server that was the primary
> source of data for this zone
> m-usage: USER_APPLICATIONS
> creatorsname: uid=admin,ou=system
> m-collective: FALSE
> m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
> m-supattributetype: apacheDnsDomainName
> m-nousermodification: FALSE
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-name: apacheDnsSoaMName
> m-equality: caseIgnoreIA5Match
> 
> because attribute files are loaded in an order that is not the one we
> can guaranty. That would be another story if the schema elements were
> not in a distinct file for each one of them.
> 
> I agree there is room for improvement here, typically not storing each
> AT, OC, etc in a separated file, but as a whole in a .schema file, as
> it's done in OpenLDAP. OTOH, that would make the schema update way more
> complex, as we would have to modify the schema file and create a new one
> for each modification, while the way we work allows us to simply update
> one single fle when we modify the schema.
> 
> It's a implementation choice.
> 
> Ideally speaking, we should mute the logs in this case, or make it a
> warning, not a error.
> 
> 
> 

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org



pEpkey.asc
Description: application/pgp-keys

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Lucas Theisen]

+1

However, test fail on Windows during attempts to delete test files.  Not
sure if that is much of a concern...

[ERROR] Errors:
[ERROR]   JdbmIndexTest.cleanup:127 ▒ IO ERR_17010_UNABLE_DELETE_FILE
Unable to delete f...
[ERROR]   JdbmRdnIndexTest.cleanup:128 ▒ IO ERR_17010_UNABLE_DELETE_FILE
Unable to delet...
[INFO]
[ERROR] Tests run: 124, Failures: 0, Errors: 2, Skipped: 0



On Aug 15, 2018 4:44 PM, "Emmanuel Lécharny"  wrote:



Le 15/08/2018 à 21:01, Stefan Seelmann a écrit :
> +1
>
> * Verified checksums and signatures
> * Built source on Linux with OpenJDK 8 and 11-ea25
> * Run installer tests:
> * bin, tar.gz and deb on Debian 9 With OpenJDK 8 and 11-ea24
> * rpm on Fedora 21 (very old!) with Java 8
>
> Note: when starting the server there is output like this:
> [18:19:00] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
> ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
> handle NameAndOptionalUID normalization with obje...

Yes, this should be a warning.

What happens is that the server will load all the schemas, recursively,
and for each schema, the AT, OC, etc Some of them are loaded before
the parts they depend on. Each of the attributeTypes and Object classes
are checked against the registries, and if they don't exist, such an
error is produced. Then a workaround is applied:

...
entry.addAttribute( attributeType, attributeValue ); //
Here, we will get an exception
}
catch ( Exception e )
{
// The attribute does not exist already, create a fake one
if ( ( schemaManager != null ) && schemaManager.isRelaxed() )
// Here, we create a fake object waiting for the real one to be loaded

Later on, when all the schemas has finally been loaded, all those
temporary objects are discarded, and a global check is done, which means
if there is some missing AT, OC or anything else, and error will be
produced.

Typically, here, an attributeType's super attribute is not yet loaded in
the registry (apacheDnsDomainName):

version: 1
dn:
m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
m-singlevalue: TRUE
m-obsolete: FALSE
m-description: The domain name of the name server that was the primary
source of data for this zone
m-usage: USER_APPLICATIONS
creatorsname: uid=admin,ou=system
m-collective: FALSE
m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
m-supattributetype: apacheDnsDomainName
m-nousermodification: FALSE
m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-name: apacheDnsSoaMName
m-equality: caseIgnoreIA5Match

because attribute files are loaded in an order that is not the one we
can guaranty. That would be another story if the schema elements were
not in a distinct file for each one of them.

I agree there is room for improvement here, typically not storing each
AT, OC, etc in a separated file, but as a whole in a .schema file, as
it's done in OpenLDAP. OTOH, that would make the schema update way more
complex, as we would have to modify the schema file and create a new one
for each modification, while the way we work allows us to simply update
one single fle when we modify the schema.

It's a implementation choice.

Ideally speaking, we should mute the logs in this case, or make it a
warning, not a error.



-- 
Emmanuel Lecharny

Symas.com
directory.apache.org

[GitHub] ccrvincent commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

ccrvincent commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21#issuecomment-41340
 
 
   @smoyer64 : No problem!  The bug tracker hadn't been migrated yet, so that's 
why I targeted the old repo.
   
   As for PATCH not being fully implemented, that's a drag for me, and I'm 
potentially going to be submitting PRs.  Turns out that the primary IdP my work 
project integrates with is deprecating Groups PUT for PATCH in _very_ short 
order.
   
   When will nightlies from the new repo become available so I can try to help 
iterate the models quickly without having to set it up in our own Jenkins?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] ccrvincent commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

ccrvincent commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21#issuecomment-41340
 
 
   @smoyer64 : No problem!  The bug tracker hadn't been migrated yet, so that's 
why I targeted the old repo.
   
   As for PATCH not being fully implemented, that's a drag for me, and I'm 
potentially going to be submitting PRs.  Turns out that the primary IdP my work 
project integrates with is deprecating Groups PUT for PATCH in _very_ short 
order.
   
   When will nightlies from the new repo become available so I can try to help 
iterate the models quickly without having to set it up in our own Jenkins?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: dist cleanup

[Emmanuel Lécharny]

I have removed the md5 files for the following projects :

* ApacheDS
* LDAP API
* JDBM
* Mavibot
* Studio

It has to be done in Fortress and kerby, let me know if you want me to
do it.

Otherwise, we should keep only the latest version of each project in
www.apache.org/dist. The older versions are still available in archives.
That means the following versions should be removed :

* Fortress 2.0.0-RC1, 2.0.0-RC2, 2.0.0
* Kerby 1.0.1
* Studio 2.0.0.v20161101-M12

Again, let me know if you want me to remove those versions.

Thanks !

Le 15/08/2018 à 20:55, Stefan Seelmann a écrit :
> On 08/15/2018 08:52 PM, Emmanuel Lécharny wrote:
>> Hi,
>>
>> there is a requirement regarding the reeases: MD5 signatures must be
>> removed for old releases :
>>
>>  -- for past releases :
>> -- you are not required to change anything ;
>> -- it would be nice if you fixed your dist area ;
>> -- start with : cleanup ; rename .sha's ; remove .md5's
>>
>> Here is a page listing the projects reeases that requires to be cleaned up:
>>
>> https://checker.apache.org/projs/directory.html
>>
>> I have started the removal of md5 signatures (for studio).
>>
>> Now, I can also re-sign all the packages with SHA-256 and SHA-512,but
>> i'm not sure it's really required.
>>
>> One of the implication is that the web pages have to be updated,
>> something I can take care of.
>>
>> WDYT ?
> 
> Is it urgent? Or sufficient to do when we anyway publish a new release?
> I mean ApacheDS should be released in 2 days, Studio will follow soon, A
> Kerby release seems also to be in preparation.
> 
> 

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org



pEpkey.asc
Description: application/pgp-keys

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Emmanuel Lécharny]

Le 15/08/2018 à 21:01, Stefan Seelmann a écrit :
> +1
> 
> * Verified checksums and signatures
> * Built source on Linux with OpenJDK 8 and 11-ea25
> * Run installer tests:
> * bin, tar.gz and deb on Debian 9 With OpenJDK 8 and 11-ea24
> * rpm on Fedora 21 (very old!) with Java 8
> 
> Note: when starting the server there is output like this:
> [18:19:00] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
> ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
> handle NameAndOptionalUID normalization with obje...

Yes, this should be a warning.

What happens is that the server will load all the schemas, recursively,
and for each schema, the AT, OC, etc Some of them are loaded before
the parts they depend on. Each of the attributeTypes and Object classes
are checked against the registries, and if they don't exist, such an
error is produced. Then a workaround is applied:

...
entry.addAttribute( attributeType, attributeValue ); //
Here, we will get an exception
}
catch ( Exception e )
{
// The attribute does not exist already, create a fake one
if ( ( schemaManager != null ) && schemaManager.isRelaxed() )
// Here, we create a fake object waiting for the real one to be loaded

Later on, when all the schemas has finally been loaded, all those
temporary objects are discarded, and a global check is done, which means
if there is some missing AT, OC or anything else, and error will be
produced.

Typically, here, an attributeType's super attribute is not yet loaded in
the registry (apacheDnsDomainName):

version: 1
dn:
m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
m-singlevalue: TRUE
m-obsolete: FALSE
m-description: The domain name of the name server that was the primary
source of data for this zone
m-usage: USER_APPLICATIONS
creatorsname: uid=admin,ou=system
m-collective: FALSE
m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
m-supattributetype: apacheDnsDomainName
m-nousermodification: FALSE
m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-name: apacheDnsSoaMName
m-equality: caseIgnoreIA5Match

because attribute files are loaded in an order that is not the one we
can guaranty. That would be another story if the schema elements were
not in a distinct file for each one of them.

I agree there is room for improvement here, typically not storing each
AT, OC, etc in a separated file, but as a whole in a .schema file, as
it's done in OpenLDAP. OTOH, that would make the schema update way more
complex, as we would have to modify the schema file and create a new one
for each modification, while the way we work allows us to simply update
one single fle when we modify the schema.

It's a implementation choice.

Ideally speaking, we should mute the logs in this case, or make it a
warning, not a error.


-- 
Emmanuel Lecharny

Symas.com
directory.apache.org



pEpkey.asc
Description: application/pgp-keys

Re: dist cleanup

[Emmanuel Lécharny]

Le 15/08/2018 à 20:55, Stefan Seelmann a écrit :
> On 08/15/2018 08:52 PM, Emmanuel Lécharny wrote:
>> Hi,
>>
>> there is a requirement regarding the reeases: MD5 signatures must be
>> removed for old releases :
>>
>>  -- for past releases :
>> -- you are not required to change anything ;
>> -- it would be nice if you fixed your dist area ;
>> -- start with : cleanup ; rename .sha's ; remove .md5's
>>
>> Here is a page listing the projects reeases that requires to be cleaned up:
>>
>> https://checker.apache.org/projs/directory.html
>>
>> I have started the removal of md5 signatures (for studio).
>>
>> Now, I can also re-sign all the packages with SHA-256 and SHA-512,but
>> i'm not sure it's really required.
>>
>> One of the implication is that the web pages have to be updated,
>> something I can take care of.
>>
>> WDYT ?
> 
> Is it urgent?

No.

 Or sufficient to do when we anyway publish a new release?

It's disconnected, IMO. We have to do it anyway, and the impact is low.

Regarding the MD5 removal, it's pretty trivial.

I'm more concerned about re-signing the old packages.

> I mean ApacheDS should be released in 2 days, Studio will follow soon, A
> Kerby release seems also to be in preparation.

In any case, we can wait before updating the web site - or at least to
publish it.

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org



pEpkey.asc
Description: application/pgp-keys

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Stefan Seelmann]

+1

* Verified checksums and signatures
* Built source on Linux with OpenJDK 8 and 11-ea25
* Run installer tests:
* bin, tar.gz and deb on Debian 9 With OpenJDK 8 and 11-ea24
* rpm on Fedora 21 (very old!) with Java 8

Note: when starting the server there is output like this:
[18:19:00] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with obje...

Kind Regards,
Stefan


On 08/14/2018 11:18 AM, Emmanuel Lecharny wrote:
> Hi,
> 
> This is a major release of ApacheDS.
> 
> It uses the Apache LDAP API 2.0.0.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 added, which is expecting to solve the
> database corruption issue we are facing for years.
> 
> 
> Here are the fixed issues :
> 
> 
> Bugs :
> --
> * DIRSERVER-2109 - Apply LDIF with special crafted DN creates two CN 
> attributes
> * DIRSERVER-2220 - ApacheDS should not log credentials
> * DIRSERVER-2231 - NPE in AbstractBTreePartition when cacheService is not used
> * DIRSERVER-2234 - Kinit via TCP causes ApacheDS to create a
> NioProcessor thread at 100% CPU
> 
> Improvements :
> --
> * DIRSERVER-2242 - Keystore change from JKS to PKCS12
> * DIRSERVER-2225 - Usage of maven-source-plugin goal jar-no-fork instead of 
> jar
> * DIRSERVER-2230 - SCM pointing to gitbox instead of svn
> * DIRSERVER-2229 - Remove duplicated declaration of
> versions-maven-plugin in pom.xml
> 
> Tasks :
> ---
> 
> * DIRSERVER-2244 - Support AES Encryption with HMAC-SHA2 for Kerberos
> 5 defined in RFC 8009
> 
>  Here are the associated links :
> 
> ApacheDS 2.0.0.AM25
> --
> - GIT tag :
> https://gitbox.apache.org/repos/asf?p=directory-server.git;a=commit;h=40ab08d93c6125ccb59d692b25759361307195d3
> - Nexus 
> repository:https://repository.apache.org/content/repositories/orgapachedirectory-1172
> 
> - Distribution packages and sources
> :https://dist.apache.org/repos/dist/dev/directory/apacheds/2.0.0.AM25/
> 
> 
> 
> [ ] +1 : release ApacheDS 2.0.0.AM25
> [ ] ± 0 : I don't care
> [ ] -1 : No, don't release ApacheDS 2.0.0.AM25
> 
> --
> Regards,
> Cordialement,
> Emmanuel Lécharnywww.iktek.com
> 
> 
> 

Re: dist cleanup

[Stefan Seelmann]

On 08/15/2018 08:52 PM, Emmanuel Lécharny wrote:
> Hi,
> 
> there is a requirement regarding the reeases: MD5 signatures must be
> removed for old releases :
> 
>  -- for past releases :
> -- you are not required to change anything ;
> -- it would be nice if you fixed your dist area ;
> -- start with : cleanup ; rename .sha's ; remove .md5's
> 
> Here is a page listing the projects reeases that requires to be cleaned up:
> 
> https://checker.apache.org/projs/directory.html
> 
> I have started the removal of md5 signatures (for studio).
> 
> Now, I can also re-sign all the packages with SHA-256 and SHA-512,but
> i'm not sure it's really required.
> 
> One of the implication is that the web pages have to be updated,
> something I can take care of.
> 
> WDYT ?

Is it urgent? Or sufficient to do when we anyway publish a new release?
I mean ApacheDS should be released in 2 days, Studio will follow soon, A
Kerby release seems also to be in preparation.

dist cleanup

[Emmanuel Lécharny]

Hi,

there is a requirement regarding the reeases: MD5 signatures must be
removed for old releases :

 -- for past releases :
-- you are not required to change anything ;
-- it would be nice if you fixed your dist area ;
-- start with : cleanup ; rename .sha's ; remove .md5's

Here is a page listing the projects reeases that requires to be cleaned up:

https://checker.apache.org/projs/directory.html

I have started the removal of md5 signatures (for studio).

Now, I can also re-sign all the packages with SHA-256 and SHA-512,but
i'm not sure it's really required.

One of the implication is that the web pages have to be updated,
something I can take care of.

WDYT ?


pEpkey.asc
Description: application/pgp-keys

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Emmanuel Lécharny]

Le 15/08/2018 à 18:19, Colm O hEigeartaigh a écrit :
> +1, built from source + tested with WSS4J/CXF.
> 
> Just a note - the link for the dist actually links to the previous release (
> https://dist.apache.org/repos/dist/dev/directory/apacheds/2.0.0-M24/).

The magic of copy/paste ;-)

Sorry...

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org



pEpkey.asc
Description: application/pgp-keys

[GitHub] smoyer64 commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

smoyer64 commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21#issuecomment-413254013
 
 
   @ccrvincent - Thanks for putting up with our migration to the Apache 
Directory project!  And thanks for the PR.  The PATCH operation within SCIMple 
is not yet fully implemented and can use as much love as it can get.  We're 
also looking into how PUT should behave when an API client that doesn't have 
permission to all stored data attempts to make an update.
   
   And don't forget to "move" your _Watch_ and _Star_ to this project!
   
   Steve


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [VOTE] Apache DS 2.0.0.AM25 release

[Colm O hEigeartaigh]

+1, built from source + tested with WSS4J/CXF.

Just a note - the link for the dist actually links to the previous release (
https://dist.apache.org/repos/dist/dev/directory/apacheds/2.0.0-M24/).

On Tue, Aug 14, 2018 at 3:36 PM, Shawn McKinney 
wrote:

>
> > 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 added, which is expecting to solve the
> > database corruption issue we are facing for years.
> >
> > ...
> >
> > [ ] +1 : release ApacheDS 2.0.0.AM25
> > [ ] ± 0 : I don't care
> > [ ] -1 : No, don't release ApacheDS 2.0.0.AM25
>
> +1, built from source, installed to centos7/java8 platform. Passed all
> tests including w/ fortress.
>
> —Arkanshawn




-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[APACHE DS] - Edit Attribute Description Help

[Marija Mrvić]

Hi, 

 

We encountered the following issue while using Apache DS
2.0.0.v20170904-M13:

 

Apache DS is intended to be used for Certificate Revocation List publishing.

 

When attribute (certificateRevocationList;binary) for the first time appears
in Apache DS while binary option is included, suffix ";binary" exists as
integral part of the attribute description. 

However, when considered attribute is updated, it can be noticed that
";binary" is missing (although the value of the attribute informs about
Binary Data).

 

I used "Edit Attribute Description" option and checked the option next to
"binary option", and could be observed that ";binary" was added to the
attribute name. 

However, as soon as I clicked on the "Finish" button, progress information
appeared about executing LDIF, and by the end of that process, ";binary" was
missing.

 

Screenshot is in the attachment of this e-mail, with added red-border field.
When checked, still produces no effect of adding suffix ";binary".

 

Furthermore, the code snippet for updating CRL is:

modificationItems.add(new ModificationItem( DirContext.REPLACE_ATTRIBUTE,
new BasicAttribute(getCrlAttributeType(), getCrl().getEncoded(;

//.this Collection is further used for modifying attributes

dirCtx.modifyAttributes(name, mods);

 

I look forward to your reply and a resolution to our problem at your most
convenient time.

 

Kind regards, 

Marija Mrvic 

[GitHub] ussmith commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

ussmith commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21#issuecomment-413211088
 
 
   Good catch


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] ussmith closed pull request #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

ussmith closed pull request #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/scim-spec/scim-spec-protocol/src/main/java/org/apache/directory/scim/spec/protocol/data/PatchOperationPathAdapter.java
 
b/scim-spec/scim-spec-protocol/src/main/java/org/apache/directory/scim/spec/protocol/data/PatchOperationPathAdapter.java
index baa07ee..103250b 100644
--- 
a/scim-spec/scim-spec-protocol/src/main/java/org/apache/directory/scim/spec/protocol/data/PatchOperationPathAdapter.java
+++ 
b/scim-spec/scim-spec-protocol/src/main/java/org/apache/directory/scim/spec/protocol/data/PatchOperationPathAdapter.java
@@ -28,7 +28,7 @@ public PatchOperationPath unmarshal(String v) throws 
Exception {
 if (v == null) {
   return null;
 }
-return new PatchOperationPath();
+return new PatchOperationPath(v);
   }
 
   @Override


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] asfgit commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

asfgit commented on issue #21: PennSt Bug #67 - PatchOperationPathAdapter 
marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21#issuecomment-413207718
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] ccrvincent opened a new pull request #21: PennSt Bug #67 - PatchOperationPathAdapter marshaller does not pass …

[GitBox]

ccrvincent opened a new pull request #21: PennSt Bug #67 - 
PatchOperationPathAdapter marshaller does not pass …
URL: https://github.com/apache/directory-scimple/pull/21
 
 
   …serialized information into object constructor.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services