Re: project & checkstyle update
On 5/11/21 4:06 AM, Emmanuel Lécharny wrote: > before we cut a LDAP API and Studio release, I have done a few updates > in the 'checkstyle' and 'project' projects. There are a hell of maven > plugin version sthat have changed since the last release. > > I checked with LDAP API and beside an issue with checkstyle ( a property > was not anymorre supported in TreeWalker), the build went fine. > > I will commit my changes in project-45 and > checkstyle-configuration-2.0.1 if no one objects. Sure, go ahead! - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
project & checkstyle update
Hi, before we cut a LDAP API and Studio release, I have done a few updates in the 'checkstyle' and 'project' projects. There are a hell of maven plugin version sthat have changed since the last release. I checked with LDAP API and beside an issue with checkstyle ( a property was not anymorre supported in TreeWalker), the build went fine. I will commit my changes in project-45 and checkstyle-configuration-2.0.1 if no one objects. Thanks ! -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRAPI-355) Binding with wrong credentials is logged in StoreMatchedDN at WARN level
[
https://issues.apache.org/jira/browse/DIRAPI-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lécharny resolved DIRAPI-355.
--
Resolution: Not A Problem
> Binding with wrong credentials is logged in StoreMatchedDN at WARN level
>
>
> Key: DIRAPI-355
> URL: https://issues.apache.org/jira/browse/DIRAPI-355
> Project: Directory Client API
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Boris Petrov
>Priority: Minor
>
> Calling `connection.bind(user, pass)` when the credentials are wrong causes:
> {noformat}
> 16:00:44.094 [NioProcessor-6] WARN o.a.d.a.l.c.a.l.StoreMatchedDN -
> MSG_05107_NO_SUCH_OBJECT_MATCHED_DN_NOT_SET ()
> {noformat}
> Which is not very nice. Entering wrong credentials is a perfectly normal
> operation and I don't see why a warning would be issued. It is annoying
> because we have to suppress these.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRAPI-367) Need to be able to Custom Add Attribute to the BinaryAttrbitueDetector
[ https://issues.apache.org/jira/browse/DIRAPI-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny updated DIRAPI-367: - Fix Version/s: 3.0.0 > Need to be able to Custom Add Attribute to the BinaryAttrbitueDetector > -- > > Key: DIRAPI-367 > URL: https://issues.apache.org/jira/browse/DIRAPI-367 > Project: Directory Client API > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Craig P Benner >Priority: Minor > Fix For: 3.0.0 > > > Note from Emmanuel: > We should really return an impl. can you fill a JIRA for that ? > Otherwise, cast the resturning value to > ConfigurableBinaryAttributeDetector : > ((ConfigurableBinaryAttributeDetector)connection.getBinaryAttributeDetector()).addBinaryAttribute( > "mS-DS-ConsistencyGuid" ) > that should do the trick (or maybe to SchemaBinaryAttributeDetector) > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRAPI-347) Async operations callbacks support
[ https://issues.apache.org/jira/browse/DIRAPI-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny updated DIRAPI-347: - Fix Version/s: 3.0.0 > Async operations callbacks support > -- > > Key: DIRAPI-347 > URL: https://issues.apache.org/jira/browse/DIRAPI-347 > Project: Directory Client API > Issue Type: Improvement >Reporter: Marcelo Cenerino >Priority: Major > Fix For: 3.0.0 > > > I would like to bring this up again given that I haven't found any Jira > tracking the original request: > [https://www.mail-archive.com/api@directory.apache.org/msg00350.html] . The > need for callback support is even more important these days I'd say. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRAPI-351) LdapTemplate and modifyTimestamp / createTimestamp
[ https://issues.apache.org/jira/browse/DIRAPI-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny resolved DIRAPI-351. -- Resolution: Not A Problem > LdapTemplate and modifyTimestamp / createTimestamp > -- > > Key: DIRAPI-351 > URL: https://issues.apache.org/jira/browse/DIRAPI-351 > Project: Directory Client API > Issue Type: Question >Affects Versions: 2.0.0.AM4 >Reporter: jaycee fineweather >Priority: Major > > Hi, > For some entries, would like to know modifyTimestamp and createTimestamp. > Unfortunately seems like it is not possible into the search method of > LdapTemplate and unavailable into the EntryMapper. > How can we do it please ? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2322) ApacheDS default server instance not starting - Error 1067
[ https://issues.apache.org/jira/browse/DIRSERVER-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSERVER-2322: --- Fix Version/s: 2.0.0.AM27 > ApacheDS default server instance not starting - Error 1067 > -- > > Key: DIRSERVER-2322 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2322 > Project: Directory ApacheDS > Issue Type: Bug > Components: installer >Affects Versions: 2.0.0.AM26 >Reporter: yangsoo song >Priority: Blocker > Labels: newbie > Fix For: 2.0.0.AM27 > > Attachments: Screen Shot 2020-07-22 at 1.58.01 PM.png > > > !Screen Shot 2020-07-22 at 1.58.01 PM.png! > Hey guys, > I followed official documents to install ApacheDS on my windows machine. I've > been trying to start the ApacheDS - default service but keep getting this > error, I've tried it on multiple machines but still getting the same message. > Has anyone encountered this issue and resolved it? > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2322) ApacheDS default server instance not starting - Error 1067
[
https://issues.apache.org/jira/browse/DIRSERVER-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342085#comment-17342085
]
Stefan Seelmann commented on DIRSERVER-2322:
I was able to get it running (it's also working with a 64bit JVM):
Installed latest AdoptOpenJDK JDK 11 64 bit (x64)
Installed ApacheDS and pointed Java Home to C:\Program
Files\AdoptOpenJDK\jdk-11.0.11.9-hotspot
Service start gave me the above error 1067. Found the following error in
{{C:\Program Files (x86)\ApacheDS\instances\default\log\wrapper.log}}:
{{java.nio.file.NoSuchFileException:
C:\WINDOWS\system32\config\systemprofile\AppData\Local\Temp\tempks15605584094397072617ks}}
After some googling I followed comments in
https://stackoverflow.com/questions/17651546/issue-in-starting-apache-ds and
https://issues.apache.org/jira/browse/DIRSERVER-2007:
Created folder {{C:\Program Files (x86)\ApacheDS\instances\default\tmp}} and
added config
{{wrapper.java.additional.6=-Djava.io.tmpdir="%INSTANCE_DIRECTORY%/tmp"}} in
{{C:\Program Files (x86)\ApacheDS\conf\wrapper.conf}}
> ApacheDS default server instance not starting - Error 1067
> --
>
> Key: DIRSERVER-2322
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2322
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: installer
>Affects Versions: 2.0.0.AM26
>Reporter: yangsoo song
>Priority: Blocker
> Labels: newbie
> Attachments: Screen Shot 2020-07-22 at 1.58.01 PM.png
>
>
> !Screen Shot 2020-07-22 at 1.58.01 PM.png!
> Hey guys,
> I followed official documents to install ApacheDS on my windows machine. I've
> been trying to start the ApacheDS - default service but keep getting this
> error, I've tried it on multiple machines but still getting the same message.
> Has anyone encountered this issue and resolved it?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2322) ApacheDS default server instance not starting - Error 1067
[ https://issues.apache.org/jira/browse/DIRSERVER-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342056#comment-17342056 ] Stefan Seelmann commented on DIRSERVER-2322: Which JVM version and arch do you use? AFAIK the Windows Installer only supports 32 bit JVMs. I'll try to verify it... > ApacheDS default server instance not starting - Error 1067 > -- > > Key: DIRSERVER-2322 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2322 > Project: Directory ApacheDS > Issue Type: Bug > Components: installer >Affects Versions: 2.0.0.AM26 >Reporter: yangsoo song >Priority: Blocker > Labels: newbie > Attachments: Screen Shot 2020-07-22 at 1.58.01 PM.png > > > !Screen Shot 2020-07-22 at 1.58.01 PM.png! > Hey guys, > I followed official documents to install ApacheDS on my windows machine. I've > been trying to start the ApacheDS - default service but keep getting this > error, I've tried it on multiple machines but still getting the same message. > Has anyone encountered this issue and resolved it? > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRAPI-357) java.lang.NoClassDefFoundError: org/apache/directory/ldap/client/api/LdapConnectionFactory
[ https://issues.apache.org/jira/browse/DIRAPI-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRAPI-357. Resolution: Cannot Reproduce Close as "cannot reproduce" as no reproduction steps were provided. Please reopen if it's still a problem. > java.lang.NoClassDefFoundError: > org/apache/directory/ldap/client/api/LdapConnectionFactory > -- > > Key: DIRAPI-357 > URL: https://issues.apache.org/jira/browse/DIRAPI-357 > Project: Directory Client API > Issue Type: Bug >Affects Versions: 2.0.1 > Environment: Java 11 >Reporter: Patrick Hub >Priority: Blocker > > I am using Apache Ldap Client API to connect to remote OpenLDAP Server. > I have add this dependency in my pom.xml file: > > org.apache.directory.api > api-all > 2.0.1 > > But when I deploy the app as war file in wildfly Every work fine. I can > performed CRUD operations on OpenLDAP Server using Apache Ldap Client API. > But when I try to deploy the app as jar file in wildfly, I get the following > error : > Caused by: java.lang.NoClassDefFoundError: > org/apache/directory/ldap/client/api/LdapConnectionFactory > at java.base/java.lang.Class.getDeclaredFields0(Native Method) > at java.base/java.lang.Class.privateGetDeclaredFields(Class.java:3062) > at java.base/java.lang.Class.getDeclaredFields(Class.java:2249) > at > org.jboss.as.server@10.0.3.Final//org.jboss.as.server.deployment.reflect.ClassReflectionIndex.(ClassReflectionIndex.java:72) > at > org.jboss.as.server@10.0.3.Final//org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) > > Please can someone help me ? > Thank > > But I have used > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRAPI-357) java.lang.NoClassDefFoundError: org/apache/directory/ldap/client/api/LdapConnectionFactory
[ https://issues.apache.org/jira/browse/DIRAPI-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRAPI-357: --- Fix Version/s: (was: 2.0.2) > java.lang.NoClassDefFoundError: > org/apache/directory/ldap/client/api/LdapConnectionFactory > -- > > Key: DIRAPI-357 > URL: https://issues.apache.org/jira/browse/DIRAPI-357 > Project: Directory Client API > Issue Type: Bug >Affects Versions: 2.0.1 > Environment: Java 11 >Reporter: Patrick Hub >Priority: Blocker > > I am using Apache Ldap Client API to connect to remote OpenLDAP Server. > I have add this dependency in my pom.xml file: > > org.apache.directory.api > api-all > 2.0.1 > > But when I deploy the app as war file in wildfly Every work fine. I can > performed CRUD operations on OpenLDAP Server using Apache Ldap Client API. > But when I try to deploy the app as jar file in wildfly, I get the following > error : > Caused by: java.lang.NoClassDefFoundError: > org/apache/directory/ldap/client/api/LdapConnectionFactory > at java.base/java.lang.Class.getDeclaredFields0(Native Method) > at java.base/java.lang.Class.privateGetDeclaredFields(Class.java:3062) > at java.base/java.lang.Class.getDeclaredFields(Class.java:2249) > at > org.jboss.as.server@10.0.3.Final//org.jboss.as.server.deployment.reflect.ClassReflectionIndex.(ClassReflectionIndex.java:72) > at > org.jboss.as.server@10.0.3.Final//org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) > > Please can someone help me ? > Thank > > But I have used > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSERVER-2322) ApacheDS default server instance not starting - Error 1067
[ https://issues.apache.org/jira/browse/DIRSERVER-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342045#comment-17342045 ] Robert Nonez commented on DIRSERVER-2322: - What can we do to get some traction on this? > ApacheDS default server instance not starting - Error 1067 > -- > > Key: DIRSERVER-2322 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2322 > Project: Directory ApacheDS > Issue Type: Bug > Components: installer >Affects Versions: 2.0.0.AM26 >Reporter: yangsoo song >Priority: Blocker > Labels: newbie > Attachments: Screen Shot 2020-07-22 at 1.58.01 PM.png > > > !Screen Shot 2020-07-22 at 1.58.01 PM.png! > Hey guys, > I followed official documents to install ApacheDS on my windows machine. I've > been trying to start the ApacheDS - default service but keep getting this > error, I've tried it on multiple machines but still getting the same message. > Has anyone encountered this issue and resolved it? > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (FC-292) User displayName attribute not updated
[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-292: -- Fix Version/s: 2.0.6 > User displayName attribute not updated > -- > > Key: FC-292 > URL: https://issues.apache.org/jira/browse/FC-292 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Admir Hodzic >Assignee: Shawn McKinney >Priority: Minor > Fix For: 2.0.6 > > Attachments: UserDisplayNameUpdate.patch > > > User displayName attribute is not getting updated by a call to > AdminMgr.updateUser. > I have created a small patch to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: API and Studio releases
Hi Stefan I'll do a quick check to see oif there is no urgent thing to push. On 10/05/2021 18:24, Stefan Seelmann wrote: Hi all, I plan to release the LDAP API [1] and afterwards Studio [2]. Let me know if some urgent fix should be included. Kind Regards, Stefan [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRAPI%20AND%20fixVersion%20%3D%202.0.2 [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRSTUDIO%20AND%20fixVersion%20%3D%202.0.0-M17 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
API and Studio releases
Hi all, I plan to release the LDAP API [1] and afterwards Studio [2]. Let me know if some urgent fix should be included. Kind Regards, Stefan [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRAPI%20AND%20fixVersion%20%3D%202.0.2 [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20DIRSTUDIO%20AND%20fixVersion%20%3D%202.0.0-M17 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1275) I updated on my mac to m16. Now only the proxy servers show the directory tree.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann reassigned DIRSTUDIO-1275: -- Assignee: Stefan Seelmann > I updated on my mac to m16. Now only the proxy servers show the directory > tree. > > > Key: DIRSTUDIO-1275 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1275 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M16 > Environment: mac os big sur 11.2.3 > apache dir server 2.0.0.v20210213-M16 >Reporter: Cathryn Major >Assignee: Stefan Seelmann >Priority: Minor > Fix For: 2.0.0-M17 > > > In apache dir studio When I open a directory server the only thing it shows > is the Root DSE. I cannot fetch the dn. > The DSE shows two name contexts-one for changelog > dc=### (not showing acutal values for dc) > For the proxy connection the DSE shows DSE2 and the components underneath it. > And these only show the dc name context. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1273) Search Logs/Modification Logs not showing up in MacOS
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1273: --- Fix Version/s: 2.0.0-M17 > Search Logs/Modification Logs not showing up in MacOS > - > > Key: DIRSTUDIO-1273 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1273 > Project: Directory Studio > Issue Type: Bug > Components: studio-rcp >Affects Versions: 2.0.0-M16 > Environment: MacOS 10.14.6 > OpenJDK16 - 16+36 - 2021-03-16 >Reporter: E M Recio >Priority: Major > Fix For: 2.0.0-M17 > > Attachments: apacheds-config-jdk11lts.txt, apacheds-config.txt > > > So I noticed that nothing is showing up in my "Search Logs" and "Modification > Logs" view. It is working just fine on Windows, but in MacOS, it's not. I am > running MacOS 10.14.6 > > I deleted my /Users/uid123/.ApacheDirectoryStudio directory, and reimported > my connections (same lbc file I used on my Windows and Linux boxes). > > On my Linux box, I removed ~/.ApacheDirectoryStudio directory, imported the > same connections LBC file, and the "Search Logs" view is working as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1274) Rework integration tests
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1274: --- Fix Version/s: 2.0.0-M17 > Rework integration tests > > > Key: DIRSTUDIO-1274 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1274 > Project: Directory Studio > Issue Type: Test >Reporter: Stefan Seelmann >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M17 > > > The SWTBot based UI tests are an important asset, the Studio test coverage is > based on that. > Those tests grew over the last years and some technical debt accumulated: > * Most UI tests run against ApacheDS only. > * Recently additional tests against OpenLDPAP and 389ds were added. However > those are separate test classes and only very few tests exist and test code > is duplicated. > * There are several LDIFs that serve as test fixture for different tests, the > increased amount makes it hard to maintain and duplication exists. > * The ApacheDS test framework is used to run an LDAP server. This framework > is currently changed to JUnit5, so changes in the Studio tests are expected > too. > It would be nice to run all UI tests against all LDAP servers > Goals: > * Allow to run all (or most) tests against multiple LDAP server (currently > ApacheDS, OpenLDAP, 389ds, more can be added) > * As there are subtle differences between LDAP servers the tests must be > aware of the server type to adjust requests or assertions > * Create a simpler and unified test fixture > * Switch to JUnit 5 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSERVER-2330) StartTlsHandler and LdapsInitializer use NoVerificationTrustManager
[ https://issues.apache.org/jira/browse/DIRSERVER-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved DIRSERVER-2330. Resolution: Fixed > StartTlsHandler and LdapsInitializer use NoVerificationTrustManager > --- > > Key: DIRSERVER-2330 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2330 > Project: Directory ApacheDS > Issue Type: Task >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0.AM27 > > > StartTlsHandler and LdapsInitializer use NoVerificationTrustManager. Instead > they should get the TrustManagers from the LdapServer, and we should have a > new annotation in CreateLdapServer to set the TrustManager classes. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[GitHub] [directory-server] coheigea merged pull request #44: DIRSERVER-2330 - StartTlsHandler and LdapsInitializer use NoVerificat…
coheigea merged pull request #44: URL: https://github.com/apache/directory-server/pull/44 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (FC-292) User displayName attribute not updated
[ https://issues.apache.org/jira/browse/FC-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-292: - Assignee: Shawn McKinney The patch does the following: # create - will use what's contained in displayName attribute if not empty, otherwise cn # modify - will update attribute, if not empty # unloadLdapEntry - load the contents pulled back from entry I'm good with these changes, although I couldn't get the patch to work, so I'll just make the coding changes for you. Thanks! > User displayName attribute not updated > -- > > Key: FC-292 > URL: https://issues.apache.org/jira/browse/FC-292 > Project: FORTRESS > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Admir Hodzic >Assignee: Shawn McKinney >Priority: Minor > Attachments: UserDisplayNameUpdate.patch > > > User displayName attribute is not getting updated by a call to > AdminMgr.updateUser. > I have created a small patch to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSERVER-2329) Replication trust manager improvements
[
https://issues.apache.org/jira/browse/DIRSERVER-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved DIRSERVER-2329.
Resolution: Fixed
> Replication trust manager improvements
> --
>
> Key: DIRSERVER-2329
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2329
> Project: Directory ApacheDS
> Issue Type: Task
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0.AM27
>
>
> There are some improvements that should be made regarding trust manager
> configuration for Replication:
> # In ReplicationTrustManager, the static block is not initialized before the
> constructor (at least in the tests), leading to a NPE.
> # SyncReplConfiguration defaults to NoVerificationTrustManager, which is not
> secure, even though this is inconsistent with the value for
> strictCertVerification (true)
> # The CreateConsumer annotation has a trustManager setting which is not used
> anywhere
> # The ServerAnnotationProcessor does not wire the value for
> CreateConsumer.{color:#00627a}strictCertVerification{color}()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSERVER-2338) Using a static IV in symmetric encryption with CBC mode
[ https://issues.apache.org/jira/browse/DIRSERVER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned DIRSERVER-2338: -- Assignee: Colm O hEigeartaigh > Using a static IV in symmetric encryption with CBC mode > --- > > Key: DIRSERVER-2338 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2338 > Project: Directory ApacheDS > Issue Type: Improvement >Reporter: Ya Xiao >Assignee: Colm O hEigeartaigh >Priority: Major > Labels: patch, security > > *Vulnerability Description* > In file > [directory-server/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java|[https://github.com/apache/directory-server/blob/master/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java],] > a hardcoded IV (at Line 161) is used to initialize the cipher (at Line 165, > Line 169). > *Security Impact:* > The IV of CBC mode is expected to be random. The static IV makes the > resulting ciphertext much more predictable and susceptible to a dictionary > attack. > *Useful Resources*: > [https://cwe.mitre.org/data/definitions/338.html|https://cwe.mitre.org/data/definitions/329.html] > *Solution we suggest* > Generate the IV bytes through SecureRandom. > *Please share with us your opinions/comments if there is any* > Is the bug report helpful? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSERVER-2338) Using a static IV in symmetric encryption with CBC mode
[ https://issues.apache.org/jira/browse/DIRSERVER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved DIRSERVER-2338. Resolution: Fixed > Using a static IV in symmetric encryption with CBC mode > --- > > Key: DIRSERVER-2338 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2338 > Project: Directory ApacheDS > Issue Type: Improvement >Reporter: Ya Xiao >Assignee: Colm O hEigeartaigh >Priority: Major > Labels: patch, security > Fix For: 2.0.0.AM27 > > > *Vulnerability Description* > In file > [directory-server/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java|[https://github.com/apache/directory-server/blob/master/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java],] > a hardcoded IV (at Line 161) is used to initialize the cipher (at Line 165, > Line 169). > *Security Impact:* > The IV of CBC mode is expected to be random. The static IV makes the > resulting ciphertext much more predictable and susceptible to a dictionary > attack. > *Useful Resources*: > [https://cwe.mitre.org/data/definitions/338.html|https://cwe.mitre.org/data/definitions/329.html] > *Solution we suggest* > Generate the IV bytes through SecureRandom. > *Please share with us your opinions/comments if there is any* > Is the bug report helpful? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2338) Using a static IV in symmetric encryption with CBC mode
[ https://issues.apache.org/jira/browse/DIRSERVER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRSERVER-2338: --- Fix Version/s: 2.0.0.AM27 > Using a static IV in symmetric encryption with CBC mode > --- > > Key: DIRSERVER-2338 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2338 > Project: Directory ApacheDS > Issue Type: Improvement >Reporter: Ya Xiao >Assignee: Colm O hEigeartaigh >Priority: Major > Labels: patch, security > Fix For: 2.0.0.AM27 > > > *Vulnerability Description* > In file > [directory-server/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java|[https://github.com/apache/directory-server/blob/master/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/crypto/encryption/DesCbcCrcEncryption.java],] > a hardcoded IV (at Line 161) is used to initialize the cipher (at Line 165, > Line 169). > *Security Impact:* > The IV of CBC mode is expected to be random. The static IV makes the > resulting ciphertext much more predictable and susceptible to a dictionary > attack. > *Useful Resources*: > [https://cwe.mitre.org/data/definitions/338.html|https://cwe.mitre.org/data/definitions/329.html] > *Solution we suggest* > Generate the IV bytes through SecureRandom. > *Please share with us your opinions/comments if there is any* > Is the bug report helpful? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[GitHub] [directory-server] coheigea merged pull request #43: DIRSERVER-2329 - Replication trust manager improvements
coheigea merged pull request #43: URL: https://github.com/apache/directory-server/pull/43 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[GitHub] [directory-server] coheigea merged pull request #46: Remove Kerberos functionality from the Directory Server
coheigea merged pull request #46: URL: https://github.com/apache/directory-server/pull/46 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Junit5 migration : done
Hi ! finally I get it completed this week-end. ALl the tests are now using Junit5, except the OSGi tests where are still dependening on PAX-exam (version 5 of this tool should support Junit5, but it's not out yet) I also have bumped up some dependencies. It builds with Maven 3.8.1, I haven't tested it with Java 11. Colm, you can move forward with the Kerberos removla (except that parts that are used for SASL tests, which require a kerberos server to be up and running, and for which we would rather use Kerby). Thanks ! -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[GitHub] [directory-kerby] dependabot[bot] opened a new pull request #100: Bump nimbus-jose-jwt from 9.9 to 9.9.3
dependabot[bot] opened a new pull request #100:
URL: https://github.com/apache/directory-kerby/pull/100
Bumps [nimbus-jose-jwt](https://bitbucket.org/connect2id/nimbus-jose-jwt)
from 9.9 to 9.9.3.
Changelog
Sourced from https://bitbucket.org/connect2id/nimbus-jose-jwt/src/master/CHANGELOG.txt;>nimbus-jose-jwt's
changelog.
version 1.0 (2012-03-01)
First version based on the OpenInfoCard JWT, JWS and JWE code base.
version 1.1 (2012-03-06)
Introduces type-safe enumeration of the JSON Web Algorithms (JWA).
Refactors the JWT class.
version 1.2 (2012-03-08)
Moves JWS and JWE code into separate classes.
version 1.3 (2012-03-09)
Switches to Apache Commons Codec for Base64URL encoding and decoding
Consolidates the crypto utilities within the package.
Introduces a JWT content serialiser class.
version 1.4 (2012-03-09)
Refactoring of JWT class and JUnit tests.
version 1.5 (2012-03-18)
Switches to JSON Smart for JSON serialisation and parsing.
Introduces claims set class with JSON objects, string, Base64URL and
byte array views.
version 1.6 (2012-03-20)
Creates class for representing, serialising and parsing JSON Web Keys
(JWK).
Introduces separate class for representing JWT headers.
version 1.7 (2012-04-01)
Introduces separate classes for plain, JWS and JWE headers.
Introduces separate classes for plain, signed and encrypted JWTs.
Removes the JWTContent class.
Removes password-based (PE820) encryption support.
version 1.8 (2012-04-03)
Adds support for the ZIP JWE header parameter.
Removes unsupported algorithms from the JWA enumeration.
version 1.9 (2012-04-03)
Renames JWEHeader.{get|set}EncryptionAlgorithm() to
JWEHeader.{get|set}EncryptionMethod().
version 1.9.1 (2012-04-03)
Upgrades JSON Smart JAR to 1.1.1.
version 1.10 (2012-04-14)
Introduces serialize() method to base abstract JWT class.
version 1.11 (2012-05-13)
JWT.serialize() throws checked JWTException instead of
... (truncated)
Commits
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/ccbc50c3a6e07c68c807676808fe2cd54d000e9f;>ccbc50c
[maven-release-plugin] prepare for next development iteration
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/72a15b043612006247ce9f10dbc83890a282923e;>72a15b0
JavaDoc pre code fixes
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/4f6573dc02c1552963c43f9ea0482c7cf2c3c368;>4f6573d
Updates release notes for 7.9 fixing CVE-2019-17195 to indicate that it also
...
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/c000d5245614e43eccfaaa07cdf0cfa87b471f4a;>c000d52
Bumps JSON Smart to 2.4.7
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/b06d211cec960d8555a8ae26c1f33199dfb464a6;>b06d211
[maven-release-plugin] prepare release 9.9.1
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/18151c73c8642193482fb8674656860b796dcb3c;>18151c7
[maven-release-plugin] prepare for next development iteration
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/3f32da37a215a4748daf3449216355aafabbedb8;>3f32da3
net.minidev:accessors-smart needs to be shaeded too
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/4a14d3582e4b42e6dfe8be09f175de0bd7b53e59;>4a14d35
Merged in master (pull request https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/77;>#77)
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/870292548e2a513088cc9c16d19d54a4f5229ecc;>8702925
Release notes for 9.9.2
https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/b8de8fc6bf67383cf25fb718cbb20a1c2aab247c;>b8de8fc
[maven-release-plugin] prepare release 9.9.2
Additional commits viewable in https://bitbucket.org/connect2id/nimbus-jose-jwt/branches/compare/9.9.3..9.9;>compare
view
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that
have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI
passes on it
- `@dependabot cancel merge` will cancel a
[GitHub] [directory-kerby] dependabot[bot] closed pull request #99: Bump nimbus-jose-jwt from 9.9 to 9.9.2
dependabot[bot] closed pull request #99: URL: https://github.com/apache/directory-kerby/pull/99 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[GitHub] [directory-kerby] dependabot[bot] commented on pull request #99: Bump nimbus-jose-jwt from 9.9 to 9.9.2
dependabot[bot] commented on pull request #99: URL: https://github.com/apache/directory-kerby/pull/99#issuecomment-836447214 Superseded by #100. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
