[studio] mvn version of artifact and the same for 'bundleversion

2024-02-13 Thread Pierre Smits
Hi all,


While working DIRSTUDIO-1304, I noticed we have for certain artifacts in
pom.xml both a 'normal' reference for the artifact and a 'bundleversion.
But not for all.

As an example:

2.1.3
2.1.3


In order to understand this (and potentially work future issues), following
popped up:

   - Why the need for both for those?
   - Is this also needed for those that currently don't have it, e.g.
   2.2
   

Met vriendelijke groet,

Pierre


[jira] [Commented] (DIRSTUDIO-1304) vulnerability for poi-3.9.jar

2024-02-13 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817084#comment-17817084
 ] 

Pierre Smits commented on DIRSTUDIO-1304:
-

locally upgrading to latest available (5.2.5) built successfully.

> vulnerability for poi-3.9.jar
> -
>
> Key: DIRSTUDIO-1304
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1304
> Project: Directory Studio
>  Issue Type: Task
>Affects Versions: 2.0.0-M17
>Reporter: Krystian Tokarz
>Assignee: Pierre Smits
>Priority: Major
> Fix For: 2.0.0-M18
>
>
> Our vulnerability system (Nessus) discovers that poi-3.9.jar file is 
> vulnerable (medium risk). This file is created when Apache Directory Studio 
> is started on our Windows 2016 Server OS.
> Folders:  
> C:\Documents and 
> Settings\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar
>  and
> C:\Users\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar
>  
> Plugin ID: 106717
> Plugin description: The version of Apache POI installed on the remote host is 
> a version prior to 3.17. It is, therefore, affected by multiple DoS 
> vulnerabilities. Note that Nessus has not tested for these issues but has 
> instead relied only on the application's self-reported version number.
> Apache POI < 3.17 Multiple DoS Vulnerabilities
>  
> Could you provide any information about this issue? Can we patch this somehow?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Assigned] (DIRSTUDIO-1304) vulnerability for poi-3.9.jar

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reassigned DIRSTUDIO-1304:
---

Assignee: Pierre Smits

> vulnerability for poi-3.9.jar
> -
>
> Key: DIRSTUDIO-1304
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1304
> Project: Directory Studio
>  Issue Type: Task
>Affects Versions: 2.0.0-M17
>Reporter: Krystian Tokarz
>Assignee: Pierre Smits
>Priority: Major
> Fix For: 2.0.0-M18
>
>
> Our vulnerability system (Nessus) discovers that poi-3.9.jar file is 
> vulnerable (medium risk). This file is created when Apache Directory Studio 
> is started on our Windows 2016 Server OS.
> Folders:  
> C:\Documents and 
> Settings\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar
>  and
> C:\Users\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar
>  
> Plugin ID: 106717
> Plugin description: The version of Apache POI installed on the remote host is 
> a version prior to 3.17. It is, therefore, affected by multiple DoS 
> vulnerabilities. Note that Nessus has not tested for these issues but has 
> instead relied only on the application's self-reported version number.
> Apache POI < 3.17 Multiple DoS Vulnerabilities
>  
> Could you provide any information about this issue? Can we patch this somehow?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Resolved] (DIRSTUDIO-1308) The Address Editor should strip trailing whitespace

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits resolved DIRSTUDIO-1308.
-
Resolution: Implemented

> The Address Editor should strip trailing whitespace
> ---
>
> Key: DIRSTUDIO-1308
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1308
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 2.0.0-M17
>Reporter: Fredrik Roubert
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0-M18
>
>
> I've had users submit postal addresses with trailing whitespace simply by 
> mistake, because they just weren't aware that they had trailing whitespace in 
> their entry.
> I can't imagine any situation in which anyone would want to have trailing 
> whitespace in a postal address, so I propose that any trailing whitespace in 
> the Address Editor should get stripped by default.
> But I also know that postal addresses in the real world are far more complex 
> than I could possibly imagine, so it'd most likely be a very good idea to 
> make it very easy to disable this stripping of trailing whitespace on a 
> case-by-case basis.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Closed] (DIRSTUDIO-1308) The Address Editor should strip trailing whitespace

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed DIRSTUDIO-1308.
---

> The Address Editor should strip trailing whitespace
> ---
>
> Key: DIRSTUDIO-1308
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1308
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 2.0.0-M17
>Reporter: Fredrik Roubert
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0-M18
>
>
> I've had users submit postal addresses with trailing whitespace simply by 
> mistake, because they just weren't aware that they had trailing whitespace in 
> their entry.
> I can't imagine any situation in which anyone would want to have trailing 
> whitespace in a postal address, so I propose that any trailing whitespace in 
> the Address Editor should get stripped by default.
> But I also know that postal addresses in the real world are far more complex 
> than I could possibly imagine, so it'd most likely be a very good idea to 
> make it very easy to disable this stripping of trailing whitespace on a 
> case-by-case basis.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Reopened] (DIRSTUDIO-1308) The Address Editor should strip trailing whitespace

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reopened DIRSTUDIO-1308:
-

fix resolution: bugs get fixed, improvements get implemented and tasks get done

> The Address Editor should strip trailing whitespace
> ---
>
> Key: DIRSTUDIO-1308
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1308
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 2.0.0-M17
>Reporter: Fredrik Roubert
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0-M18
>
>
> I've had users submit postal addresses with trailing whitespace simply by 
> mistake, because they just weren't aware that they had trailing whitespace in 
> their entry.
> I can't imagine any situation in which anyone would want to have trailing 
> whitespace in a postal address, so I propose that any trailing whitespace in 
> the Address Editor should get stripped by default.
> But I also know that postal addresses in the real world are far more complex 
> than I could possibly imagine, so it'd most likely be a very good idea to 
> make it very easy to disable this stripping of trailing whitespace on a 
> case-by-case basis.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Closed] (DIRSTUDIO-1286) Windows installer: the software version is missing

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed DIRSTUDIO-1286.
---

> Windows installer: the software version is missing
> --
>
> Key: DIRSTUDIO-1286
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-installer
>Affects Versions: 2.0.0-M17
> Environment: Windows 10
>Reporter: Elvis Bortoletto
>Assignee: Pierre Smits
>Priority: Minor
> Fix For: 2.0.0-M18
>
> Attachments: image-2021-08-17-18-31-32-731.png, 
> image-2021-08-17-18-32-47-581.png
>
>
> Once installed the Directory Studio, the version is not reported in "Control 
> Panel | Programs and Features".
> !image-2021-08-17-18-32-47-581.png!
> As a side effect, "winget upgrade" gets confused, reporting the Directory 
> Studio in the list of the packages with an available upgrade.
> !image-2021-08-17-18-31-32-731.png!
> Maybe reporting the software version would enhance the user experience and 
> would fix the winget behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Resolved] (DIRSTUDIO-1286) Windows installer: the software version is missing

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits resolved DIRSTUDIO-1286.
-
Resolution: Implemented

> Windows installer: the software version is missing
> --
>
> Key: DIRSTUDIO-1286
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-installer
>Affects Versions: 2.0.0-M17
> Environment: Windows 10
>Reporter: Elvis Bortoletto
>Assignee: Pierre Smits
>Priority: Minor
> Fix For: 2.0.0-M18
>
> Attachments: image-2021-08-17-18-31-32-731.png, 
> image-2021-08-17-18-32-47-581.png
>
>
> Once installed the Directory Studio, the version is not reported in "Control 
> Panel | Programs and Features".
> !image-2021-08-17-18-32-47-581.png!
> As a side effect, "winget upgrade" gets confused, reporting the Directory 
> Studio in the list of the packages with an available upgrade.
> !image-2021-08-17-18-31-32-731.png!
> Maybe reporting the software version would enhance the user experience and 
> would fix the winget behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Reopened] (DIRSTUDIO-1286) Windows installer: the software version is missing

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reopened DIRSTUDIO-1286:
-

correcting status and resolution

> Windows installer: the software version is missing
> --
>
> Key: DIRSTUDIO-1286
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-installer
>Affects Versions: 2.0.0-M17
> Environment: Windows 10
>Reporter: Elvis Bortoletto
>Assignee: Pierre Smits
>Priority: Minor
> Fix For: 2.0.0-M18
>
> Attachments: image-2021-08-17-18-31-32-731.png, 
> image-2021-08-17-18-32-47-581.png
>
>
> Once installed the Directory Studio, the version is not reported in "Control 
> Panel | Programs and Features".
> !image-2021-08-17-18-32-47-581.png!
> As a side effect, "winget upgrade" gets confused, reporting the Directory 
> Studio in the list of the packages with an available upgrade.
> !image-2021-08-17-18-31-32-731.png!
> Maybe reporting the software version would enhance the user experience and 
> would fix the winget behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-567) Would be cool to expose SchemaObject in a LDIF format

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-567:
---
Fix Version/s: (was: 2.0.0)

> Would be cool to expose SchemaObject in a LDIF format
> -
>
> Key: DIRSTUDIO-567
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-567
> Project: Directory Studio
>  Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Emmanuel Lécharny
>Priority: Minor
>
> SchemaObjects are exposed in two different formats :
> - a template editor
> - a OpenLDAP format
> It would be cool to have it exposed as a LDIF format (for ADS or for OpendLAP 
> too)
> That could be an optional selection activated in the preferences, where you 
> give all the possible representation for a ShcemaObject with the associated 
> editors for them (we may have many different ways to manipulate a 
> SchemaObject, depending on the server)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-1019) LDIF editor can't open files bigger than 1Mb

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-1019:

Fix Version/s: (was: 2.0.0)

> LDIF editor can't open files bigger than 1Mb
> 
>
> Key: DIRSTUDIO-1019
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1019
> Project: Directory Studio
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> There is a hard coded size limit for LDIF files in the LDIF editor :
> {code}
> if ( fileLength > ( 1 * 1024 * 1024 ) )
> {
> MessageDialog.openError( site.getShell(), Messages.getString( 
> "LdifEditor.LDIFFileIsTooBig" ),
> Messages.getString( 
> "LdifEditor.LDIFFileIsTooBigDescription" ) ); 
> ...
> {code}
> It would be better to use a size which is defined in the preference.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-87) Add actions to the entry editor outline view

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-87:
--
Fix Version/s: (was: 2.0.0)

> Add actions to the entry editor outline view
> 
>
> Key: DIRSTUDIO-87
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-87
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 0.6.0, 0.7.0
>Reporter: Stefan Seelmann
>Priority: Minor
>
> Currently the outline view just displays the attributes and values. We should 
> also add actions to the outline view. It should be possible reuse the 
> existing actions from the entry editor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-1029) Code Signing

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-1029:

Fix Version/s: (was: 2.0.0)

> Code Signing
> 
>
> Key: DIRSTUDIO-1029
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1029
> Project: Directory Studio
>  Issue Type: Improvement
>Reporter: Stefan Seelmann
>Priority: Major
>
> The ASF now has a code signing servers. Maybe we can/should use it to sign 
> Studio jars to avoid warnings when installing the Studio plugins within 
> Eclipse.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-842) We should be able to "create" a new server based on an existing server

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-842:
---
Fix Version/s: (was: 2.0.0)

> We should be able to "create" a new server based on an existing server
> --
>
> Key: DIRSTUDIO-842
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-842
> Project: Directory Studio
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M3 (2.0.0.v20120224)
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> Currently, the "new server" creation will create embedded server. When one 
> has already installed a server on the local machine it would be a good thing 
> to allow this user to "create" (or "refer") this existing server, allowing 
> the configuration of this external server.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-626) Value editor for 'member'

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-626:
---
Fix Version/s: (was: 2.0.0)

> Value editor for 'member'
> -
>
> Key: DIRSTUDIO-626
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-626
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 1.5.2
>Reporter: Ari Maniatis
>Priority: Major
>
> Value editors can already be extended as per 
> http://cwiki.apache.org/confluence/display/DIRxSTUDIO/Value+Editor+Extension+Point
> Although there is an old old task DIRSTUDIO-22 for improving usability with 
> common entities (such as groupOfNames), a simpler first step improvement 
> would be to create an editor for the common "member" attribute. It should be 
> capable of resolving the DN value to the CN of the related record. A brief 
> discussion was had here: http://markmail.org/message/vi3uyjkennzdu727
> This improvement would make a huge difference to the ease of managing LDAP 
> directories which use groupOfNames extensively.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-645) Improve handling of large data sets

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-645:
---
Fix Version/s: (was: 2.0.0)

> Improve handling of large data sets
> ---
>
> Key: DIRSTUDIO-645
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-645
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-connection, studio-ldapbrowser
>Reporter: Stefan Seelmann
>Priority: Major
>
> When requesting large data sets in the browser or in a search Studio becomes 
> utilizes much memory and CPU.
> One issue is that we hold the recieved entries in memory. Emmanuel suggested 
> to test ehcache that makes it easy to move some data to disk.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-566) Would be cool to be able to export a single schema object as LDIF or OpenLDAP format

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-566:
---
Fix Version/s: (was: 2.0.0)

> Would be cool to be able to export a single schema object as LDIF or OpenLDAP 
> format
> 
>
> Key: DIRSTUDIO-566
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-566
> Project: Directory Studio
>  Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> Currently, we can only export Schema Objects as a whole (ie, the Schema is 
> the unit), not a single AT or OC only.
> We could not either save it in the clipboard, which forces you to select a 
> path or a file, when a paste in an editor would have been way more convenient.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-561) Create Schema plugins

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-561:
---
Fix Version/s: (was: 2.0.0)

> Create Schema plugins
> -
>
> Key: DIRSTUDIO-561
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-561
> Project: Directory Studio
>  Issue Type: Improvement
>Reporter: Stefan Seelmann
>Priority: Major
>
> We should create a schema plugin (core and ui, similar to the 
> connections.core and connections.ui plugins) that includes all schema 
> functionality used in studio. This includes core components like consistency 
> check, but also UI components. Then those components could be used by both, 
> the ldapbrowser and the schemaedtitor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-750) Directory Studio should propose the control "server side sort"

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-750:
---
Fix Version/s: (was: 2.0.0)

> Directory Studio should propose the control "server side sort" 
> ---
>
> Key: DIRSTUDIO-750
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-750
> Project: Directory Studio
>  Issue Type: New Feature
>  Components: studio-ldapbrowser
>Affects Versions: 1.5.3
> Environment: non Apache Directory LDAP directories
>Reporter: Thomas
>Priority: Minor
>  Labels: Server, side, sort, sss
>
> Many people use Apache Directory Studio against other directories than 
> Apaches ( I use it against Novell Edirectory) Most of these other directories 
> support "Server Side Sort" (SSS) and it is a shame Directory Studio does not.
> Especially seeing that all the mechanics is in place - just need to add the 
> case SSS in the dialog: file, export, LDAP to LDIF (under controls).
> You COULD make the appearance of the control dependent of the existence of 
> the control on the Root DSE to not cconfuse users of Apache Directory Server.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Closed] (DIRSTUDIO-1277) Update ApacheDS to support Java 16+

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed DIRSTUDIO-1277.
---

> Update ApacheDS to support Java 16+
> ---
>
> Key: DIRSTUDIO-1277
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1277
> Project: Directory Studio
>  Issue Type: Task
>Affects Versions: 2.0.0-M16, 2.0.0-M17
>Reporter: Stefan Seelmann
>Priority: Major
> Fix For: 2.0.0-M16
>
>
> The current ApacheDS version 2.0.0.AM26 doesn't work with Java 16+. It fails 
> at startup with 
> {noformat}
> Exception in thread "main" java.lang.IllegalAccessError: class 
> org.apache.directory.server.core.security.CertificateUtil (in unnamed module 
> @0x2ef0d60d) cannot access class sun.security.x509.X500Name (in module 
> java.base) because module java.base does not export sun.security.x509 to 
> unnamed module @0x2ef0d60d
> at 
> org.apache.directory.server.core.security.CertificateUtil.createTempKeyStore(CertificateUtil.java:334)
> at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:219)
> at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:152)
> at org.apache.directory.server.UberjarMain.start(UberjarMain.java:153)
> at org.apache.directory.server.UberjarMain.main(UberjarMain.java:80)
> {noformat}
> In 
> https://github.com/apache/directory-studio/commit/4b7335cac568bdc8a9df8dda55c82e0745edaf87
>  some tests were disabled which should be re-enabled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Resolved] (DIRSTUDIO-1277) Update ApacheDS to support Java 16+

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits resolved DIRSTUDIO-1277.
-
Fix Version/s: 2.0.0-M16
   (was: 2.0.0)
   Resolution: Implemented

> Update ApacheDS to support Java 16+
> ---
>
> Key: DIRSTUDIO-1277
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1277
> Project: Directory Studio
>  Issue Type: Task
>Affects Versions: 2.0.0-M16, 2.0.0-M17
>Reporter: Stefan Seelmann
>Priority: Major
> Fix For: 2.0.0-M16
>
>
> The current ApacheDS version 2.0.0.AM26 doesn't work with Java 16+. It fails 
> at startup with 
> {noformat}
> Exception in thread "main" java.lang.IllegalAccessError: class 
> org.apache.directory.server.core.security.CertificateUtil (in unnamed module 
> @0x2ef0d60d) cannot access class sun.security.x509.X500Name (in module 
> java.base) because module java.base does not export sun.security.x509 to 
> unnamed module @0x2ef0d60d
> at 
> org.apache.directory.server.core.security.CertificateUtil.createTempKeyStore(CertificateUtil.java:334)
> at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:219)
> at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:152)
> at org.apache.directory.server.UberjarMain.start(UberjarMain.java:153)
> at org.apache.directory.server.UberjarMain.main(UberjarMain.java:80)
> {noformat}
> In 
> https://github.com/apache/directory-studio/commit/4b7335cac568bdc8a9df8dda55c82e0745edaf87
>  some tests were disabled which should be re-enabled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-766) Localize Apache Directory Studio in Spanish

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-766:
---
Fix Version/s: (was: 2.0.0)

> Localize Apache Directory Studio in Spanish
> ---
>
> Key: DIRSTUDIO-766
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-766
> Project: Directory Studio
>  Issue Type: Improvement
>Reporter: Pierre-Arnaud Marcelot
>Priority: Major
>
> Localize Apache Directory Studio in Spanish



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-766) Localize Apache Directory Studio in Spanish

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-766:
---
Issue Type: Improvement  (was: Task)

> Localize Apache Directory Studio in Spanish
> ---
>
> Key: DIRSTUDIO-766
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-766
> Project: Directory Studio
>  Issue Type: Improvement
>Reporter: Pierre-Arnaud Marcelot
>Priority: Major
> Fix For: 2.0.0
>
>
> Localize Apache Directory Studio in Spanish



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-709) Add support for password policy request and response controls

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-709:
---
Fix Version/s: (was: 2.0.0)

> Add support for password policy request and response controls
> -
>
> Key: DIRSTUDIO-709
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-709
> Project: Directory Studio
>  Issue Type: New Feature
>Reporter: Kiran Ayyagari
>Priority: Minor
>
> Adding support for the controls[1] as specified in the password policy draft 
> [2]
> [1] http://tools.ietf.org/html/draft-behera-ldap-password-policy-10#section-6
> [2] http://tools.ietf.org/html/draft-behera-ldap-password-policy-10



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-787) Add support for shared bookmarks across all connections

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-787:
---
Fix Version/s: (was: 2.0.0)

> Add support for shared bookmarks across all connections
> ---
>
> Key: DIRSTUDIO-787
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-787
> Project: Directory Studio
>  Issue Type: New Feature
>  Components: studio-ldapbrowser
>Reporter: Pierre-Arnaud Marcelot
>Assignee: Pierre-Arnaud Marcelot
>Priority: Major
>
> It would be interesting to be able to have bookmarks that are shared across 
> all connections.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-786) Add support for shared searches across all connections

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-786:
---
Fix Version/s: (was: 2.0.0)

> Add support for shared searches across all connections
> --
>
> Key: DIRSTUDIO-786
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-786
> Project: Directory Studio
>  Issue Type: New Feature
>  Components: studio-ldapbrowser
>Reporter: Pierre-Arnaud Marcelot
>Assignee: Pierre-Arnaud Marcelot
>Priority: Major
>
> It would be interesting to be able to have searches that are shared across 
> all connections.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-800) Add a convertor from .schema to OpenLDAP LDIF format

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-800:
---
Fix Version/s: (was: 2.0.0)

> Add a convertor from .schema to OpenLDAP LDIF format
> 
>
> Key: DIRSTUDIO-800
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-800
> Project: Directory Studio
>  Issue Type: New Feature
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> That would be great to be able to convert a .schema file into a LDIF file 
> that OpenLDAP can swallow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-732) apache directory studio don't support OID Macros

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-732:
---
Fix Version/s: (was: 2.0.0)

> apache directory studio don't support OID Macros
> 
>
> Key: DIRSTUDIO-732
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-732
> Project: Directory Studio
>  Issue Type: New Feature
>  Components: studio-schemaeditor
>Affects Versions: 1.5.3
> Environment: windows XP; Open LDAP 2.4 directory
>Reporter: Francois PICHOUD
>Priority: Major
>
> I have 2 attribute that have macro ID : x.y.z:1 and x.y.z:2  
> ADS just saw the first one. 
> It had been solve on shared project : DIRSHARED-10



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-707) It would be cool to have a button to fold/unfold all the file or the selected lines globally

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-707:
---
Fix Version/s: (was: 2.0.0)

> It would be cool to have a button to fold/unfold all the file or the selected 
> lines globally
> 
>
> Key: DIRSTUDIO-707
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-707
> Project: Directory Studio
>  Issue Type: New Feature
>  Components: studio-ldifeditor
>Affects Versions: 1.5.3
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> If I select some lines, or the file file (or if no lines are selected), it 
> would be very convenient to have a button that fold/unfold the selected lines 
> or the entire file. Right now, if I want tofold many lines, I have to click 
> each of the line that can be folded one by one.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-662) Numbered attributes not showing up in TRUE numerical order; should be at least an option.

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-662:
---
Fix Version/s: (was: 2.0.0)

> Numbered attributes not showing up in TRUE numerical order; should be at 
> least an option.
> -
>
> Key: DIRSTUDIO-662
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-662
> Project: Directory Studio
>  Issue Type: Improvement
>  Components: studio-ldapbrowser
>Affects Versions: 1.5.3
> Environment: Apple OS X 10.6.3
>Reporter: gropefruit
>Priority: Minor
>  Labels: Ordering, numbering, views
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Some attributes, when housing multiple values, are numbered:
> {0} value
> {1} value
> ...
> ...
> Though when you get up to multiple digit-numbers, the numerical ordering gets 
> out of hand:
> {0} 
> {1} 
> {10} 
> {11} 
> {2} 
> {3} 
> ...
> ...
> An option should at least exist to allow attributes to be returned in TRUE 
> numerical order:
> {0} 
> {1} 
> {2} 
> {3} 
> ...
> ..
> {10} 
> {11} 
> ..
> ..
> I do not believe this is a bug, yet I do not believe it should be a feature 
> request.  Therefore, I feel this should be listed as an IMPROVEMENT.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-543) Need some editors for N,C,SC in the browser

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-543:
---
Fix Version/s: (was: 2.0.0)

> Need some editors for  N,C,SC in the browser
> 
>
> Key: DIRSTUDIO-543
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-543
> Project: Directory Studio
>  Issue Type: New Feature
>Affects Versions: 1.4.0
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> Would be quite cool to be able to inject a 
> Normalizer/SyntaxChecker/Comparator into the server when modifying the schema 
> in ADS.
> The idea is to have a value editor for those schema element, where you can 
> select a .class file implementing the associated C/N/SC, which will be 
> serialized in the schema element and sent to the server.
> This is of course specific to ADS, so the editor should only be active for a 
> ADSConnection



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-542) Need some editors for AT, OC, MR, S, NF, MRU, DSR,DCR in the browser

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-542:
---
Fix Version/s: (was: 2.0.0)

> Need some editors for AT, OC, MR, S, NF, MRU, DSR,DCR  in the browser
> -
>
> Key: DIRSTUDIO-542
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-542
> Project: Directory Studio
>  Issue Type: New Feature
>Affects Versions: 1.4.0
>Reporter: Emmanuel Lécharny
>Priority: Major
>
> It would be cool to have some dedicated value editosr in the browser, when 
> doing some modification on the schema.
> We have the AT and OC value editor in the schema browser, we could use them 
> in the ldap browser. We also have to add those value editors :
> - MR (MatchingRule)
> - S (Syntax)
> - MRU (MatchingRuleUse)
> - NF (NameForm)
> - DCR (Dit Control Rule)
> - DSR (Dit Structure Rule)
> Those are not specifically ADS editors



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSTUDIO-1315) Upgrade xmlgraphics-commons to 2.6

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSTUDIO-1315:

Summary: Upgrade xmlgraphics-commons to 2.6  (was: Upgrade 
xmlgraphics-commons)

> Upgrade xmlgraphics-commons to 2.6
> --
>
> Key: DIRSTUDIO-1315
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1315
> Project: Directory Studio
>  Issue Type: Improvement
>    Reporter: Pierre Smits
>    Assignee: Pierre Smits
>Priority: Major
>
> dependabot https://github.com/apache/directory-studio/pull/39



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Created] (DIRSTUDIO-1315) Upgrade xmlgraphics-commons

2024-02-13 Thread Pierre Smits (Jira)
Pierre Smits created DIRSTUDIO-1315:
---

 Summary: Upgrade xmlgraphics-commons
 Key: DIRSTUDIO-1315
 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1315
 Project: Directory Studio
  Issue Type: Improvement
Reporter: Pierre Smits
Assignee: Pierre Smits


dependabot https://github.com/apache/directory-studio/pull/39



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Created] (DIRSERVER-2392) Update Copyright year

2024-02-13 Thread Pierre Smits (Jira)
Pierre Smits created DIRSERVER-2392:
---

 Summary: Update Copyright year 
 Key: DIRSERVER-2392
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2392
 Project: Directory ApacheDS
  Issue Type: Improvement
Reporter: Pierre Smits
Assignee: Pierre Smits


in notice



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



Dependabot pull-requests

2024-02-13 Thread Pierre Smits
Hi all,

Since way back when the dependabot bots of our reposities create
pull-request.

In various repositories our committers have merged these requests directly.
However, these merges don't show up in our releases, as there are no
corresponding tickets in our JIRAs

How should we handle this?

Met vriendelijke groet,

Pierre


[jira] [Closed] (DIRSERVER-2391) Update forbidden apis plugin to 3.6

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed DIRSERVER-2391.
---

commit 
[https://github.com/apache/directory-server/commit/a9cb7238fd80aeb6a82fd47504cdade2dfee77e6]
 merged into the main branch by bdemers

> Update forbidden apis plugin to 3.6
> ---
>
> Key: DIRSERVER-2391
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2391
> Project: Directory ApacheDS
>  Issue Type: Improvement
>Affects Versions: 2.0.0.AM27
>    Reporter: Pierre Smits
>Priority: Major
> Fix For: Upcoming release
>
>
> referencing pull-request https://github.com/apache/directory-server/pull/88



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Created] (DIRSERVER-2391) Update forbidden apis plugin to 3.6

2024-02-13 Thread Pierre Smits (Jira)
Pierre Smits created DIRSERVER-2391:
---

 Summary: Update forbidden apis plugin to 3.6
 Key: DIRSERVER-2391
 URL: https://issues.apache.org/jira/browse/DIRSERVER-2391
 Project: Directory ApacheDS
  Issue Type: Improvement
Affects Versions: 2.0.0.AM27
Reporter: Pierre Smits
 Fix For: Upcoming release


referencing pull-request https://github.com/apache/directory-server/pull/88



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-997) Block search ability for userPassword attribute

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-997:
---
Fix Version/s: (was: 2.0.0-RC1)
   (was: 2.0.0-M8)

> Block search ability for userPassword attribute
> ---
>
> Key: DIRSERVER-997
> URL: https://issues.apache.org/jira/browse/DIRSERVER-997
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: aci, config
>Affects Versions: pre-1.0, 1.0-RC1, 1.0-RC2, 1.0-RC3, 1.0-RC4, 1.0, 1.0.1, 
> 1.0.2, 1.5.0, 1.5.1, 1.5.2
> Environment: All
>Reporter: Hans Lohmander
>Assignee: Emmanuel Lécharny
>Priority: Major
>
> I entered this issue on request from the user list where this topic came up.
> The userPassword should not be available for search,
> else password fishing is possible.
> If you are allowed to do a search like
> $ ldapsearch -b o=some.root -s sub 
> 'userPassword="{md5}b4b5835f03bd6748e0cc25790d6f3498"' dn
> it would render you all objects with the attribute userPassword equal to
> "the secret password", which may not be such a good idea.
> iPlanet DS 4.x allowed searches on ueserPassword attribute with
> directory manager privs I found out. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-1954) Second startup of an embedded server fails (after an ungraceful shutdown of the first startup)

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-1954:

Fix Version/s: (was: 2.0.0-M16)

> Second startup of an embedded server fails (after an ungraceful shutdown of 
> the first startup)
> --
>
> Key: DIRSERVER-1954
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1954
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: jdbm
>Affects Versions: 2.0.0-M14
>Reporter: Bouke Nijhuis
>Priority: Major
> Attachments: EmbeddedADSVerTrunk.java, EmbeddedADSVerTrunkV2.java, 
> after_first_run.png, after_second_run.png, apacheds.log, console.png, 
> example.zip
>
>
> I have created an embedded server based on the code from:
> http://svn.apache.org/repos/asf/directory/sandbox/kayyagari/embedded-sample-trunk/src/main/java/org/apache/directory/seserver/EmbeddedADSVerTrunk.java
> I slimmed it down (removed code for creating partitions/indices) so it only 
> starts a DirectoryService and LdapServer. I will attach the source code of 
> the class.
> The first run goes as expected. Everything runs smooth:
> log4j:WARN No appenders could be found for logger 
> (org.apache.directory.server.core.api.CacheService).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> The server is running.
> Then I stop the process by using the square red button in the console window 
> of Eclipse. I will add a screenshot. I think this will kill the JVM, but I am 
> not sure.
> The second run always fails with the following error:
> log4j:WARN No appenders could be found for logger 
> (org.apache.directory.server.core.api.CacheService).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> schema partition already exists, skipping schema extraction
> org.apache.directory.api.ldap.model.exception.LdapEntryAlreadyExistsException:
>  ERR_250_ENTRY_ALREADY_EXISTS ou=system already exists!
>   at 
> org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.add(AbstractBTreePartition.java:615)
>   at 
> org.apache.directory.server.core.DefaultDirectoryService.initializeSystemPartition(DefaultDirectoryService.java:1770)
>   at 
> org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:1827)
>   at 
> org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:1253)
>   at 
> server.EmbeddedADSVerTrunk.initDirectoryService(EmbeddedADSVerTrunk.java:164)
>   at server.EmbeddedADSVerTrunk.(EmbeddedADSVerTrunk.java:178)
>   at server.EmbeddedADSVerTrunk.main(EmbeddedADSVerTrunk.java:215)
> The third run will be smooth again.So will the fourth, fifth, etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2283) ApacheDS graceful shutdown automatically

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2283:

Fix Version/s: (was: 2.0.0-M24)

> ApacheDS graceful shutdown automatically
> 
>
> Key: DIRSERVER-2283
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2283
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: ldap
>Affects Versions: 2.0.0-M24
> Environment: Linux
>Reporter: Leo
>Priority: Major
>
> I found that apacheds "Attempting graceful shutdown of the service..." and 
> then restart. But sometimes just shutdown and not restart. Why? Is it a bug?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2091) Server Side Sort Control Broken in 2.0.0 M20

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2091:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Server Side Sort Control Broken in 2.0.0 M20
> 
>
> Key: DIRSERVER-2091
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2091
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: control
>Affects Versions: 2.0.0-M20
>Reporter: Danil Flores
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: hunderd-users.ldif, logerror.txt, sort-result.ldif
>
>
> Given a partition with several objects with objectClass=inetOrgPerson, we 
> want to be able to perform a search with a server-side-sort request control. 
> The following ldapsearch query was giving the correct results in ApacheDS 
> 2.0.0 M19:
> ldapsearch -H ldap://localhost:10389 -x -D "uid=admin,ou=system" -W -b 
> "dc=example,dc=com" -s sub -a always -z 1000 "(objectClass=inetOrgPerson)" 
> "objectClass" -E sss=-cn:2.5.13.2
> However in ApacheDS 2.0.0 M20, we get the following error upon running the 
> same query against a similar data set:
> # search result
> search: 2
> result: 54 Loop detected
> text: LOOP_DETECT: failed for MessageType : SEARCH_REQUEST
> Message ID : 2
>
>   SearchRequest
> baseDn : 'dc=example,dc=com'
> filter : '(objectCla
>  ss=inetorgperson:[5])'
> scope : whole subtree
> typesOnly : false
> Size Limit : 1000
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes : 'objectClass'
> org.apache.directory.api.ldap.model.message.SearchRequestImpl@38b18ca0SortRequestControlImpl
>  [sortKeys=[SortKey : [cn, 2.5.13.2,reverse]]]: java.io.IOException: The 
> system cannot find the path specified



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2081) ApacheDS taking up to 30 seconds stop stop politely

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2081:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> ApacheDS taking up to 30 seconds stop stop politely
> ---
>
> Key: DIRSERVER-2081
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2081
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: ldap
>Affects Versions: 2.0.0-M20
>Reporter: lucas theisen
>Assignee: Kiran Ayyagari
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: forgotpassword_schema.ldif, portalperson_schema.ldif
>
>
> To reproduce:
> # {{svn update}} to the _-M21-SNAPSHOT_
> # Unpack an archive apacheds
> # Tune your {{$ADS_HOME/insances/default/conf/log4j.properties}} as follows:
> ## {code}
> log4j.logger.org.apache.directory.server.core.DefaultDirectoryService=ALL
> log4j.logger.org.apache.directory.server.config=INFO
> log4j.logger.org.apache.directory.server.UberjarMain=ALL
> {code}
> # From $ADS_HOME
> ## {code}
> cd instances/default/;
> rm -rf .dirservice.lock partitions/* cache/* log/* run/* run/.s* 
> syncrepl-data/*;
> cd ../..;
> bin/apacheds.sh start
> {code}
> ## In a separate window
> ### {{tail -f $ADS_HOME/instances/default/log/apacheds.out}}
> ## Import the attached {{.ldif}} files (i dont think the specifics of the 
> ldif files matters)
> ## {{apacheds.sh stop}}
> This is not 100% of the time, but if done fairly close together, you should 
> see the log look something like this:
> {code}
> [16:22:23] INFO [org.apache.directory.server.UberjarMain] - Stopping the 
> service.
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> +++ DirectoryService Shutdown required
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> --- Syncing the nexus
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> --- Flushing everything before quitting
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> --- Syncing the changeLog
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> --- Destroying the nexus
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> --- Deleting the cache service
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> ---Deleting the DnCache
> [16:22:23] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> +++ DirectoryService stopped
> [16:22:23] INFO [org.apache.directory.server.UberjarMain] - Service stopped 
> successfully.
> [16:22:43] DEBUG [org.apache.directory.server.core.DefaultDirectoryService] - 
> +++ DirectoryService Shutdown required
> {code}
> And you can see that the last log message was 10's of seconds after the 
> initial shutdown request.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2144) Role Disappreared

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2144:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Role Disappreared
> -
>
> Key: DIRSERVER-2144
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2144
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: jdbm
>Affects Versions: 2.0.0-M16
>Reporter: Siddharth Thakar
>Priority: Major
> Fix For: Upcoming release
>
>
> I have very strange problem on my production environment.
> There was below entry present and lots of users were assigned to group 
> GEBRUIKER, suddenly group GEBRUIKER disappeared and all users belongs to that 
> group no longer able to login to the system.
> cn=GEBRUIKER,ou=roles,ou=groups,dc=lgronline,dc=nl
> When I try to create the group again it gives me error 
> #!ERROR ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST Message ID 
> : 25 Add Request : Entry dn[n]: 
> cn=GEBRUIKER,ou=roles,ou=groups,dc=lgronline,dc=nl objectclass: 
> organizationalRole objectclass: top cn: GEBRUIKER description: 
> ERR_250_ENTRY_ALREADY_EXISTS 
> cn=GEBRUIKER,ou=roles,ou=groups,dc=lgronline,dc=nl already exists!
> dn: cn=GEBRUIKER,ou=roles,ou=groups,dc=lgronline,dc=nl
> changetype: add
> Please someone help to resolve this issue.
> I even restored that /var/lib/apacheds-2.0.0-M16 directory from last month 
> hoping that user might have done some wrong and one month old restore will 
> fix the issue, however issue is still there, not getting any help online as 
> well.
> SOS



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2147) The ObjectClass index is using the ObjectClass name and not its OID

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2147:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> The ObjectClass index is using the ObjectClass name and not its OID
> ---
>
> Key: DIRSERVER-2147
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2147
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: search
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> The {{ObjectClass}} index is using the name as the index's key, instead of 
> the OID. This is problematic because an {{ObjectClass}} may have more than 
> one name, as {{AttributeType}} may.
> The Index should use teh {{ObjectClass}}' OID



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-1986) Delegated authentication fails when password policy is enabled

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-1986:

Fix Version/s: (was: 2.0.0-M18)

> Delegated authentication fails when password policy is enabled 
> ---
>
> Key: DIRSERVER-1986
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1986
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: authn
>Affects Versions: 2.0.0-M16
>Reporter: Kiran Ayyagari
>Priority: Critical
>
> In the AuthenticationInterceptor's bind() method tries to apply password 
> policy on a user entry that is present in the other LDAP server used by the 
> DelegatedAuthenticator.
> This clearly fails cause the user is not a local user. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2148) A Search on an Attribute that does not have a Substring MatchingRule should always do a full scan

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2148:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> A Search on an Attribute that does not have a Substring MatchingRule should 
> always do a full scan
> -
>
> Key: DIRSERVER-2148
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2148
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: search
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> Searches using a filter like {{(ObjectClass=org*)}} should do a full scan, as 
> the {{ObjectClass}} attributeType does not have a {{SUBSTRING}} matching rule 
> :
> {noformat}
> attributetype ( 2.5.4.0 
>   NAME 'objectClass' 
>   DESC 'RFC2256: object classes of the entity' 
>   EQUALITY objectIdentifierMatch 
>   SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 
>  )
> {noformat}
> Currently, we bypass this missing {{SUBSTRING}} matching rule, by using a 
> default substring search. This is wrong. In this very case, the search should 
> return nothing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-1891) http-integration jetty9 support

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-1891:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> http-integration jetty9 support
> ---
>
> Key: DIRSERVER-1891
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1891
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: http
>Affects Versions: 2.0.0-M15
>Reporter: gil cattaneo
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: apacheds-2.0.0-M15-http-integration-jetty9.patch
>
>
> i created a patch for add jetty 9.x support to http-integration module
> i would be grateful if you could give me some help or suggestion to improve it
> regards



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2149) Searching with a >= or <= filter when we don't have a ORDERING MR should not give back a result

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2149:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Searching with a >= or <= filter when we don't have a ORDERING MR should not 
> give back a result
> ---
>
> Key: DIRSERVER-2149
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2149
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: search
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> Doing a search like {{(street >= 1)}} should simply return nothing, because 
> the {{street}} attributeType does not have an {{ORDERING}} MatchingRule.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2077) Provide tools to migrate the config or the data between releases

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2077:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Provide tools to migrate the config or the data between releases
> 
>
> Key: DIRSERVER-2077
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2077
> Project: Directory ApacheDS
>  Issue Type: Task
>  Components: tools
>Affects Versions: 2.0.0-M20
>Reporter: Emmanuel Lécharny
>Priority: Critical
> Fix For: Upcoming release
>
>
> We have been lazy in the past, by not provided tools to migrate from one 
> version to the other, simply because they were milestones.
> There are three things we need to migrate :
> - configuration 
> - schemas
> - data
> for each of those data, we have to provide a tool that helps the migration 
> from one version to the next one.
> Ideally, this should be cumulative : ie, migrating from N to, say, N+3 should 
> migrate those data from N to N+1, then N+1 to N+2 and finally N+2 to N+3



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2068) Failed to decrypt a timestamp if it was encrypted with non-best-fit algo

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2068:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Failed to decrypt a timestamp if it was encrypted with non-best-fit algo
> 
>
> Key: DIRSERVER-2068
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2068
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: core
>Affects Versions: 2.0.0-M20
>Reporter: Alexander Bersenev
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: preauth.patch
>
>
> Suppose the client supports two encryption suites:
> default_tkt_enctypes = des-cbc-md5 des3-cbc-sha1-kd
> Server also supports three encryption suites: 
> des-cbc-md5, des3-cbc-sha1-kd and aes128-cts-hmac-sha1-96
> The client send as-req with list of supported ciphers. Server answers the 
> client with three ciphers.
> The client chooses des-cbc-md5 and sends as-req with encrypted timestamp.
> The bug is here. The server can try to decrypt timestamp with wrong 
> algo(des3-cbc-sha1-kd). This occurs because of function 
> getBestEncryptionType( Set requestedTypes,
> Set configuredTypes )
> returns some encryption type that both client and server support. It not 
> necessary the cipher that was used to encrypt the timestamp.
> Attached patch does decryption of timestamp always with cipher it was 
> encrypted(if the server is configured to support that cipher)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2104) Renaming an entry which uses a SINGLE-VALUE attribute in the RDN fails

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2104:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Renaming an entry which uses a SINGLE-VALUE attribute in the RDN fails
> --
>
> Key: DIRSERVER-2104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2104
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: ldap
>Affects Versions: 2.0.0-M20
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> There is a test ({{LdifPartitionTest.testLdifRenameAndRetainOldDN}}) that 
> does a rename, trying to keep the old RDN present :
> {code}
> Rdn newRdn = new Rdn( "dc=renamedChild1" );
> RenameOperationContext renameOpCtx = new RenameOperationContext( 
> session, childDn1, newRdn, false );
> partition.rename( renameOpCtx );
> ...
> // the renamed LDIF must contain the old an new Rdn attribute
> String content = FileUtils.readFileToString( new File( wkdir, 
> "ou=test,ou=system/dc=renamedchild1.ldif" ) );
> assertTrue( content.contains( "dc: child1" ) );
> assertTrue( content.contains( "dc: renamedchild1" ) );
> {code}
> The past passes green which is really problematic : the {{DC}} AttributeType 
> is supposed to be SINGLE-VALUE !!!
> {code}
> attributetype ( 0.9.2342.19200300.100.1.25 NAME ( 'dc' 'domainComponent' )
>   DESC 'RFC1274/2247: domain component'
>   EQUALITY caseIgnoreIA5Match
>   SUBSTR caseIgnoreIA5SubstringsMatch
>   SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
>   SINGLE-VALUE
>   USAGE userApplications
> )
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2115) ERR_04269 ATTRIBUTE_TYPE for OID ads-hashalgorithm does not exist

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2115:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

>  ERR_04269 ATTRIBUTE_TYPE for OID ads-hashalgorithm does not exist
> --
>
> Key: DIRSERVER-2115
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2115
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: ldap, schema
>Affects Versions: 2.0.0-M20
> Environment: Windows 7
>Reporter: Jose L ortuno 
>Priority: Major
> Fix For: Upcoming release
>
>
> After upgrading to 2.0.0-M-21. Directory Server is not able star.
> C:\utils\apacheds-2.0.0-M21\bin>apacheds.bat
> Starting ApacheDS instance 'default'...
> [17:29:05] WARN [org.apache.directory.api.ldap.model.entry.DefaultEntry] - 
> The attribute 'ads-hashalgorithm' cannot be stored
> [17:29:05] ERROR [org.apache.directory.server.UberjarMain] - Failed to start 
> the service.
> org.apache.directory.api.ldap.model.exception.LdapOtherException: ERR_04269 
> ATTRIBUTE_TYPE for OID ads-hashalgorithm does not exist!
> at 
> org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:94)
> at 
> org.apache.directory.server.config.ConfigPartitionInitializer.initConfigPartition(ConfigPartitionInitializer.java:197)
> at 
> org.apache.directory.server.ApacheDsService.initConfigPartition(ApacheDsService.java:289)
> at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:172)
> at org.apache.directory.server.UberjarMain.start(UberjarMain.java:136)
> at org.apache.directory.server.UberjarMain.main(UberjarMain.java:76)
> Caused by: 
> org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: 
> ERR_04269 ATTRIBUTE_TYPE for OID ads-hashalgorithm does not ex
> st!
> at 
> org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:293)
> at 
> org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:47)
> at 
> org.apache.directory.api.ldap.schema.manager.impl.DefaultSchemaManager.lookupAttributeTypeRegistry(DefaultSchemaManager.java:1604)
> at 
> org.apache.directory.api.ldap.model.entry.DefaultEntry.(DefaultEntry.java:311)
> at 
> org.apache.directory.server.core.partition.ldif.LdifPartition.loadEntries(LdifPartition.java:518)
> at 
> org.apache.directory.server.core.partition.ldif.LdifPartition.loadEntries(LdifPartition.java:550)
> at 
> org.apache.directory.server.core.partition.ldif.LdifPartition.loadEntries(LdifPartition.java:550)
> at 
> org.apache.directory.server.core.partition.ldif.LdifPartition.loadEntries(LdifPartition.java:550)
> at 
> org.apache.directory.server.core.partition.ldif.LdifPartition.doInit(LdifPartition.java:165)
> at 
> org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:89)
> ... 5 more
> Caused by: org.apache.directory.api.ldap.model.exception.LdapException: 
> ERR_04269 ATTRIBUTE_TYPE for OID ads-hashalgorithm does not exist!
> at 
> org.apache.directory.api.ldap.model.schema.registries.DefaultSchemaObjectRegistry.lookup(DefaultSchemaObjectRegistry.java:224)
> at 
> org.apache.directory.api.ldap.model.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:289)
> ... 14 more
> [17:29:05] ERROR [org.apache.directory.server.UberjarMain] - Failed to start 
> the service.
> java.lang.NullPointerException
> at 
> org.apache.directory.server.ApacheDsService.stop(ApacheDsService.java:577)
> at org.apache.directory.server.UberjarMain.stop(UberjarMain.java:155)
> at org.apache.directory.server.UberjarMain.start(UberjarMain.java:143)
> at org.apache.directory.server.UberjarMain.main(UberjarMain.java:76)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2116) ApacheDS failed to start after every reboot and throwing error ERR_250_ENTRY_ALREADY_EXISTS dc=example,dc=com already exists!

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2116:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> ApacheDS failed to start after every reboot and throwing error 
> ERR_250_ENTRY_ALREADY_EXISTS dc=example,dc=com already exists!
> -
>
> Key: DIRSERVER-2116
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2116
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: jdbm
>Affects Versions: 2.0.0-M21
> Environment: Ubuntu 14.04.3 LTS trusty
>Reporter: AADI
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: complete-dump-2017-02-07.ldif, 
> org.apache.directory.studio.ldapservers-2017-02-07.zip, 
> org.apache.directory.studio.ldapservers-2017-02-07.zip
>
>
> HI 
> I downloaded ApcheDS Debian Package (apacheds-2.0.0-M21-amd64.deb ) 
> and installed on Ubuntu server for my personal testing of LDAP .
> It worked very well after i installed and configured on my server .
> But problems arise when my server rebooted every-time . 
> After every reboot i have to start the  ApacheDS server manually  by follwing 
> command 
> *sudo /etc/init.d/apacheds-2.0.0-M21-default start
> And immediately i got following reply 
> Starting ApacheDS - default...
> ApacheDS - default is already running. *
> But this is not true. i observed there is no process running which are 
> associated with ApacheDS  in OS 
> After referring the one of the solution given in this list i just clear the 
> pid file contents ( 
> /var/lib/apacheds-2.0.0-M21/default/run/apacheds-default.pid) and overcome 
> the first problem .
> But still it failed to start and i observed below errors in log file 
> {color:red}
> {{jvm 1| [15:51:29] ERROR 
> [org.apache.directory.server.wrapper.ApacheDsTanukiWrapper] - Failed to start 
> the service.
> jvm 1| org.apache.directory.api.ldap.model.exception.LdapOtherException: 
> ERR_250_ENTRY_ALREADY_EXISTS dc=example,dc=com already exists!
> jvm 1|at 
> org.apache.directory.server.core.api.partition.AbstractPartition.initialize(AbstractPartition.java:94)
> jvm 1|at 
> org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:1813)
> jvm 1|at 
> org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:1250)
> jvm 1|at 
> org.apache.directory.server.ApacheDsService.initDirectoryService(ApacheDsService.java:318)
> jvm 1|at 
> org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:182)
> jvm 1|at 
> org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.start(ApacheDsTanukiWrapper.java:72)
> jvm 1|at 
> org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) 
> }}{color} 
> i would like to know that should i reinstall the ApacheDS evertyime when 
> server reboot ?
> i tried several solutions mentioned in web to overcome this none worked for 
> me except reinstall 
>  
>   



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2360) Windows Installer for ApacheDS 2.0.0-M27

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2360:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Windows Installer for ApacheDS 2.0.0-M27
> 
>
> Key: DIRSERVER-2360
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2360
> Project: Directory ApacheDS
>  Issue Type: Task
>  Components: build
>Reporter: Paul Jones
>Priority: Major
> Fix For: Upcoming release
>
>
> When will we have a windows installer for AM27?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2382) Log message about account locked after too many failed log in attempts

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2382:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Log message about account locked after too many failed log in attempts
> --
>
> Key: DIRSERVER-2382
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2382
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: authn
>Affects Versions: 2.0.0.AM26
>Reporter: Oleksandr Andreiev
>Priority: Major
> Fix For: Upcoming release
>
>
> Hello,
> I've discovered that there are no any logs about account locked after max 
> failed log ins event logged.
> It might be useful for tracking auth activity metric.
> Did I miss something and it is present? Otherwise, are there plans to add it?
> Regards,
> Oleksandr 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2153:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: backend, ldap
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2216) Data corruption with the export

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2216:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Data corruption with the export
> ---
>
> Key: DIRSERVER-2216
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2216
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: installer-plugin
> Environment: Windows
>Reporter: prisy cherian
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: ldap_backup_2017-12-28_13-13-15.ldif
>
>
> Hi,
> We are using Apache DS in Windows for an year now.
> We started with 50 users for development and everything was working as 
> expected.
> We scheduled backups every 2 hours.
> Later in Production, LDAP data hangs & Search stops to work throwing USER NOT 
> FOUND or LDAP Connection Timeout Exception or  Attribute not found etc. The 
> exception differs every time, eventually we found out in one of the back up 
> files that it is Data Corruption. 
> Everytime, we had to restore the backup & it is more than 10 times by now.
> We have around 11,000 users now. We schedule backup every day.
> We found a similar issue happening in M17 & M20 with the large number of user 
> import-export.
> Is this issue with JDBM Backend is still in M24 also? 
> Can you please suggest ?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2182) Apaches 2.0.0-M23 embedded instance cannot run correctly within docker container

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2182:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Apaches 2.0.0-M23 embedded instance cannot run correctly within docker 
> container
> 
>
> Key: DIRSERVER-2182
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2182
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0.0-M23
> Environment: ApacheDS Embedded instance, dropwizard and Docker 2.x
>Reporter: harish sat
>Priority: Major
> Fix For: Upcoming release
>
>
> While running current instance within docker container, the ldapserver does 
> not bind on a specified port, no error message or exception thrown. It works 
> fine as a standalone instance but there is a problem within docker container



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2224) To provide "Idle Connection timeout" feature in Apache-DS.

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2224:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> To provide "Idle Connection timeout" feature in Apache-DS. 
> ---
>
> Key: DIRSERVER-2224
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2224
> Project: Directory ApacheDS
>  Issue Type: Wish
>  Components: network
>Affects Versions: 2.0.0-M24
>Reporter: virupaksh ankad
>Priority: Minor
>  Labels: performance
> Fix For: Upcoming release
>
>
> Hello,
> In context with the query that was posted earlier 
> (http://mail-archives.apache.org/mod_mbox/directory-users/201801.mbox/browser),
>   To protect from LDAP clients who may use large connection pools, we are 
> looking at terminating connections after certain period of inactivity, this 
> is a request to the Apache-DS development team to provide a configurable 
> "Idle Connection timeout" feature.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2206) RefinementEvaluator fails when "objectClass" attribute is not present in the list of attributes

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2206:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> RefinementEvaluator fails when "objectClass" attribute is not present in the 
> list of attributes
> ---
>
> Key: DIRSERVER-2206
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2206
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: aci
>Affects Versions: 2.0.0-M24
>Reporter: Kiran Ayyagari
>Priority: Major
> Fix For: Upcoming release
>
> Attachments: allowreadusers.ldif
>
>
> I have a ACI that filters entries based on the the {{classes}} protected item 
> but when
> the search request doesn't contain {{objectClass}} in the requested 
> attributes the below
> exception is thrown.
> {noformat}
> org.apache.directory.api.ldap.model.message.SearchRequestImpl@c452319: 
> ERR_296 objectClasses cannot be null:
> java.lang.IllegalArgumentException: ERR_296 objectClasses cannot be null
>   at 
> org.apache.directory.server.core.api.subtree.RefinementEvaluator.evaluate(RefinementEvaluator.java:65)
>   at 
> org.apache.directory.server.core.authz.support.RelatedProtectedItemFilter.isRelated(RelatedProtectedItemFilter.java:213)
>   at 
> org.apache.directory.server.core.authz.support.RelatedProtectedItemFilter.filter(RelatedProtectedItemFilter.java:86)
>   at 
> org.apache.directory.server.core.authz.support.ACDFEngine.hasPermission(ACDFEngine.java:160)
>   at 
> org.apache.directory.server.core.authz.AciAuthorizationInterceptor.filter(AciAuthorizationInterceptor.java:1368)
>   at 
> org.apache.directory.server.core.authz.AciAuthorizationInterceptor.access$200(AciAuthorizationInterceptor.java:91)
>   at 
> org.apache.directory.server.core.authz.AciAuthorizationInterceptor$AuthorizationFilter.accept(AciAuthorizationInterceptor.java:1428)
>   at 
> org.apache.directory.server.core.api.filtering.EntryFilteringCursorImpl.next(EntryFilteringCursorImpl.java:454)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.writeResults(SearchRequestHandler.java:380)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.doSimpleSearch(SearchRequestHandler.java:840)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.handleIgnoringReferrals(SearchRequestHandler.java:1164)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.handleWithReferrals(SearchRequestHandler.java:1258)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.handle(SearchRequestHandler.java:212)
>   at 
> org.apache.directory.server.ldap.handlers.request.SearchRequestHandler.handle(SearchRequestHandler.java:92)
>   at 
> org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:222)
>   at 
> org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:56)
>   at 
> org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:243)
>   at 
> org.apache.directory.server.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:216)
>   at 
> org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:858)
>   at 
> org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:542)
>   at 
> org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300(DefaultIoFilterChain.java:48)
>   at 
> org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:947)
>   at 
> org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:74)
>   at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
>   at 
> org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.runTask(UnorderedThreadPoolExecutor.java:476)
>   at 
> org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.run(UnorderedThreadPoolExecutor.java:430)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Steps to reproduce:
> # Apply the allowreadusers.ldif
> # restart the server
> # run the command ldapsearch -H ldap://localhost:10389 -D "" -b 
> "uid=kayyagari,ou=Users,dc=example,dc=com" -s base -a al

[jira] [Updated] (DIRSERVER-2279) PasswordModify extended request does not work when there are multiple passwords

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2279:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> PasswordModify extended request does not work when there are multiple 
> passwords
> ---
>
> Key: DIRSERVER-2279
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2279
> Project: Directory ApacheDS
>  Issue Type: Task
>  Components: pwd interceptor
>Affects Versions: 2.0.0.AM25
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> Sending a {{passwordModify}} extended request to change an old password to a 
> new one does not work properly if there is more than one password in the 
> entry. The problem is that all the old passwords are removed, even those 
> which are not requested to be removed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2254) Package for MacOSX cannot be opened, due to a lack of Apple developer signature

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2254:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> Package for MacOSX cannot be opened, due to a lack of Apple developer 
> signature
> ---
>
> Key: DIRSERVER-2254
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2254
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0.0.AM25
>Reporter: Emmanuel Lécharny
>Priority: Critical
> Fix For: Upcoming release
>
>
> Since {{Mac OS X Sierra}}, installers must be signed with a Apple developer 
> key. {{ApacheDS}} latest package isn't.
> We need to follow the steps from 
> [INFRA-16978|https://issues.apache.org/jira/browse/INFRA-16978] to get it 
> working.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2313) 2.0.0.M26: Invalid signature file digest for Manifest main attributes

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2313:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> 2.0.0.M26: Invalid signature file digest for Manifest main attributes
> -
>
> Key: DIRSERVER-2313
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2313
> Project: Directory ApacheDS
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0.0.AM26
>Reporter: Jan Van Ryckeghem
>Priority: Critical
> Fix For: Upcoming release
>
>
> JAR can't be verified:
> {code:java}
> ~/.m2/repository/org/apache/directory/server/apacheds-all/2.0.0.AM26
> $ jarsigner -verify -verbose apacheds-all-2.0.0.AM26.jar
> jarsigner: java.lang.SecurityException: Invalid signature file digest for 
> Manifest main attributes{code}
> This breaks projects using OWASP Vulnerability scanning.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Commented] (OFBIZ-12892) Screen Classifications in Party should not show create trigger to user with only VIEW permission

2024-02-09 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-12892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815961#comment-17815961
 ] 

Pierre Smits commented on OFBIZ-12892:
--

Thanks [~jleroux], for your assistance in getting this into the codebase.

> Screen Classifications in Party should not show create trigger to user with 
> only VIEW permission
> 
>
> Key: OFBIZ-12892
> URL: https://issues.apache.org/jira/browse/OFBIZ-12892
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Upcoming Branch
>    Reporter: Pierre Smits
>Priority: Major
>
> When accessing 
> [https://demo-trunk.ofbiz.apache.org/partymgr/control/showclassgroups] as a 
> user with only VIEW permissions (e.g. userId = auditor) the action trigger to 
> create a new Party Classification Group is shown.
> This should not be visible to such a user as it leads to an undesired effect 
> and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12895) Have screen ListLoggedInUsers show Party MainActionMenu

2024-02-06 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12895:


 Summary: Have screen ListLoggedInUsers show Party MainActionMenu
 Key: OFBIZ-12895
 URL: https://issues.apache.org/jira/browse/OFBIZ-12895
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


Currently the ListLoggedInUsers screen in VisitScreens.xml does not show the 
MainActionMenu of the party component.

For a consistent user experience this should be.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (OFBIZ-12891) Screen Communications in Party should not show create trigger to user with VIEW permissions

2024-02-06 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed OFBIZ-12891.

Resolution: Implemented

Thanks [~jleroux] for getting this into the codebase.

> Screen Communications in Party should not show create trigger to user with 
> VIEW permissions
> ---
>
> Key: OFBIZ-12891
> URL: https://issues.apache.org/jira/browse/OFBIZ-12891
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Upcoming Branch
>    Reporter: Pierre Smits
>Priority: Major
>  Labels: user-experience
>
> When accessing 
> [https://demo-trunk.ofbiz.apache.org/partymgr/control/FindCommunicationEvents]
>  as a user with only VIEW permissions (.e.g. userId = auditor) the action 
> trigger to create a new communication is shown.
>  
> This should not be visible to such a user as it leads to an undesired effect 
> and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OFBIZ-12891) Screen Communications in Party should not show create trigger to user with VIEW permissions

2024-02-06 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-12891:
-
Labels: user-experience  (was: )

> Screen Communications in Party should not show create trigger to user with 
> VIEW permissions
> ---
>
> Key: OFBIZ-12891
> URL: https://issues.apache.org/jira/browse/OFBIZ-12891
> Project: OFBiz
>  Issue Type: Improvement
>  Components: party
>Affects Versions: Upcoming Branch
>    Reporter: Pierre Smits
>Priority: Major
>  Labels: user-experience
>
> When accessing 
> [https://demo-trunk.ofbiz.apache.org/partymgr/control/FindCommunicationEvents]
>  as a user with only VIEW permissions (.e.g. userId = auditor) the action 
> trigger to create a new communication is shown.
>  
> This should not be visible to such a user as it leads to an undesired effect 
> and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12893) Screen Security in Party should not show create trigger to user with only VIEW permission.

2024-02-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12893:


 Summary: Screen Security in Party should not show create trigger 
to user with only VIEW permission.
 Key: OFBIZ-12893
 URL: https://issues.apache.org/jira/browse/OFBIZ-12893
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://demo-trunk.ofbiz.apache.org/partymgr/control/FindSecurityGroup] as a 
user with only VIEW permissions (e.g. userId = auditor) the action trigger to 
create something is shown.

This should not be visible to such a user as it leads to an undesired effect 
and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12892) Screen Classifications in Party should not show create trigger to user with only VIEW permission

2024-02-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12892:


 Summary: Screen Classifications in Party should not show create 
trigger to user with only VIEW permission
 Key: OFBIZ-12892
 URL: https://issues.apache.org/jira/browse/OFBIZ-12892
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://demo-trunk.ofbiz.apache.org/partymgr/control/showclassgroups] as a 
user with only VIEW permissions (e.g. userId = auditor) the action trigger to 
create a new Party Classification Group is shown.

This should not be visible to such a user as it leads to an undesired effect 
and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12891) Screen Communications in Party should not show create trigger to user with VIEW permissions

2024-02-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12891:


 Summary: Screen Communications in Party should not show create 
trigger to user with VIEW permissions
 Key: OFBIZ-12891
 URL: https://issues.apache.org/jira/browse/OFBIZ-12891
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://demo-trunk.ofbiz.apache.org/partymgr/control/FindCommunicationEvents] 
as a user with only VIEW permissions (.e.g. userId = auditor) the action 
trigger to create a new communication is shown.

 

This should not be visible to such a user as it leads to an undesired effect 
and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: building Atlas

2023-06-13 Thread Pierre Smits
Hi Nixon,

Thank you very much. That did it.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory <https://directory.apache.org>, PMC Member*

Anyone could have been you, whereas I've always been anyone.


On Fri, Jun 9, 2023 at 10:19 AM Nixon Rodrigues  wrote:

> Pierre,
>
> you can apply this fix and try.
>
> https://github.com/apache/atlas/pull/219/files
>
> On Wed, 7 Jun 2023 at 19:52, Pierre Smits  wrote:
>
> > Hi all,
> >
> > In a goal to implement Atlas in my private dev environment, I downloaded
> > the file re 2.3.0 and started the build with:
> >
> > mvn clean -DskipTests install
> >
> >
> > However, it didn't complete. The error I got was:
> >
> > [*ERROR*] Failed to execute goal on project atlas-testtools: *Could not
> > resolve dependencies for project
> > org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to collect
> dependencies
> > at org.apache.solr:solr-test-framework:jar:8.6.3 ->
> > org.restlet.jee:org.restlet:jar:2.4.3*: Failed to read artifact
> descriptor
> > for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact
> > org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet (
> > https://maven.restlet.com): Transfer failed for
> >
> >
> https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom
> > :
> > PKIX path validation failed:
> java.security.cert.CertPathValidatorException:
> > validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> *[Help
> 1]*
> >
> > Is there a way to correct, circumvent this?
> >
> > Any help would be greatly appreciated
> >
> >
> > Met vriendelijke groet,
> >
> > Pierre Smits
> > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/>
> since
> > 2008 (without privileges)
> > Proud contributor to the ASF since 2006
> > *Apache Directory <https://directory.apache.org>, PMC Member*
> >
> > Anyone could have been you, whereas I've always been anyone.
> >
>


building Atlas

2023-06-07 Thread Pierre Smits
Hi all,

In a goal to implement Atlas in my private dev environment, I downloaded
the file re 2.3.0 and started the build with:

mvn clean -DskipTests install


However, it didn't complete. The error I got was:

[*ERROR*] Failed to execute goal on project atlas-testtools: *Could not
resolve dependencies for project
org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to collect dependencies
at org.apache.solr:solr-test-framework:jar:8.6.3 ->
org.restlet.jee:org.restlet:jar:2.4.3*: Failed to read artifact descriptor
for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact
org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet (
https://maven.restlet.com): Transfer failed for
https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom:
PKIX path validation failed: java.security.cert.CertPathValidatorException:
validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> *[Help 1]*

Is there a way to correct, circumvent this?

Any help would be greatly appreciated


Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory <https://directory.apache.org>, PMC Member*

Anyone could have been you, whereas I've always been anyone.


[jira] [Commented] (AMBARI-25497) problems with AMBARI Installation Guide

2023-06-07 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17730027#comment-17730027
 ] 

Pierre Smits commented on AMBARI-25497:
---

re: #1

The same applies to version 2.7.7

> problems with AMBARI Installation Guide
> ---
>
> Key: AMBARI-25497
> URL: https://issues.apache.org/jira/browse/AMBARI-25497
> Project: Ambari
>  Issue Type: Documentation
>Reporter: Tiger Wang
>Priority: Major
>
> [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.5]
>  
> *1. RAT is complaing too many unapproved licenses*
> Which can be solved by
>  
> changing 
>  
> {{mvn -B clean install jdeb:jdeb -DnewVersion=2.7.5.0.0 
> -DbuildNumber=5895e4ed6b30a2da8a90fee2403b6cab91d19972 -DskipTests 
> -Dpython.ver="python >= 2.6"}}
>  
> to
>  
> {{mvn -B clean install jdeb:jdeb -DnewVersion=2.7.5.0.0 
> -DbuildNumber=5895e4ed6b30a2da8a90fee2403b6cab91d19972 -DskipTests 
> -Dpython.ver="python >= 2.6" *{color:#ff8b00}-Drat.skip=true{color}*}}
>  
> *2. node version is too old that it causes ambari-admin failed to build.*
>  
> Should add a step to update ambari-admin/pom.xml with changes like
>  
> {{v10.19.0}}
> {{ 6.13.4}}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org



[jira] [Commented] (ATLAS-4760) Unable to build Atlas project due to various dependency issues

2023-06-07 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/ATLAS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1772#comment-1772
 ] 

Pierre Smits commented on ATLAS-4760:
-

I experience the same on Ubuntu 20.04.

The error I get is:
{code:java}
[ERROR] Failed to execute goal on project atlas-testtools: Could not resolve 
dependencies for project org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to 
collect dependencies at org.apache.solr:solr-test-framework:jar:8.6.3 -> 
org.restlet.jee:org.restlet:jar:2.4.3: Failed to read artifact descriptor for 
org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact 
org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet 
(https://maven.restlet.com): Transfer failed for 
https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom:
 PKIX path validation failed: java.security.cert.CertPathValidatorException: 
validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> [Help 1] {code}

> Unable to build Atlas project due to various dependency issues
> --
>
> Key: ATLAS-4760
> URL: https://issues.apache.org/jira/browse/ATLAS-4760
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.3.0
> Environment: -- cat /etc/os-release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/;
> --   uname -r
> 4.14.313-235.533.amzn2.x86_64
>Reporter: Udaykiran Reddy
>Priority: Major
>
> Unable to build Atlas project due to various dependency issues
> Java - 1.8
> Maven - 3.9.2
> Atlas version  - 2.3.0 – 
> [https://atlas.apache.org/2.3.0/index.html#/Downloads] 
> Error
> {code:java}
> [INFO] 
> 
> [INFO] Reactor Summary for apache-atlas 2.3.0:
> [INFO] 
> [INFO] Apache Atlas Server Build Tools  SUCCESS [  3.395 
> s]
> [INFO] apache-atlas ... SUCCESS [ 10.087 
> s]
> [INFO] Apache Atlas Integration ... SUCCESS [ 15.802 
> s]
> [INFO] Apache Atlas Test Utility Tools  FAILURE [  4.474 
> s]
> [INFO] Apache Atlas Common  SKIPPED
> [INFO] Apache Atlas Client  SKIPPED
> [INFO] atlas-client-common  SKIPPED
> [INFO] atlas-client-v1  SKIPPED
> [INFO] Apache Atlas Server API  SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] atlas-client-v2  SKIPPED
> [INFO] Apache Atlas Graph Database Projects ... SKIPPED
> [INFO] Apache Atlas Graph Database API  SKIPPED
> [INFO] Graph Database Common Code . SKIPPED
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SKIPPED
> [INFO] Apache Atlas JanusGraph DB Impl  SKIPPED
> [INFO] Apache Atlas Graph DB Dependencies . SKIPPED
> [INFO] Apache Atlas Authorization . SKIPPED
> [INFO] Apache Atlas Repository  SKIPPED
> [INFO] Apache Atlas UI  SKIPPED
> [INFO] Apache Atlas New UI  SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader  SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim  SKIPPED
> [INFO] Apache Atlas Falcon Bridge . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
> [INFO] Apache Atlas Sqoop Bridge .. SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim . SKIPPED
> [INFO] Apache Atlas Storm Bridge .. SKIPPED
> [INFO] Apache Atlas Hbase Bridge Shim . SKIPPED
> [INFO] Apache Atlas Hbase Bridge .. SKIPPED
>

[jira] [Updated] (OFBIZ-12819) PaymentGroup Create button shown to viewer

2023-05-12 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-12819:
-
Description: Currently when a user with only view permissions accesses the 
PaymentGroup overview, as shown in demo-trunk with userid=auditor, the action 
trigger to create a new PaymentGroup is shown. See attached image.  (was: 
Currently when a user with only view permissions, as shown in demo-trunk with 
userid=auditor, the action trigger to create a new PaymentGroup is shown. See 
attached image.)

> PaymentGroup Create button shown to viewer
> --
>
> Key: OFBIZ-12819
> URL: https://issues.apache.org/jira/browse/OFBIZ-12819
> Project: OFBiz
>  Issue Type: Bug
>  Components: accounting
>Affects Versions: Upcoming Branch
>Reporter: Pierre Smits
>Priority: Major
> Attachments: Screenshot from 2023-05-12 11-22-03.png
>
>
> Currently when a user with only view permissions accesses the PaymentGroup 
> overview, as shown in demo-trunk with userid=auditor, the action trigger to 
> create a new PaymentGroup is shown. See attached image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12820) PaymentGroup Cancel button is shown to viewer

2023-05-12 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12820:


 Summary: PaymentGroup Cancel button is shown to viewer
 Key: OFBIZ-12820
 URL: https://issues.apache.org/jira/browse/OFBIZ-12820
 Project: OFBiz
  Issue Type: Bug
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits
 Attachments: Screenshot from 2023-05-12 11-53-42.png

Currently when a user with only view permissions accesses the PaymentGroup 
overview, as demonstrated in demo-trunk with userid=auditor, the action trigger 
to cancel a PaymentGroup is shown. See attached image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12819) PaymentGroup Create button shown to viewer

2023-05-12 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12819:


 Summary: PaymentGroup Create button shown to viewer
 Key: OFBIZ-12819
 URL: https://issues.apache.org/jira/browse/OFBIZ-12819
 Project: OFBiz
  Issue Type: Bug
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits
 Attachments: Screenshot from 2023-05-12 11-22-03.png

Currently when a user with only view permissions, as shown in demo-trunk with 
userid=auditor, the action trigger to create a new PaymentGroup is shown. See 
attached image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12818) request PaymentAcctgTransEntriesPdf throws an error

2023-05-12 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12818:


 Summary: request PaymentAcctgTransEntriesPdf throws an error
 Key: OFBIZ-12818
 URL: https://issues.apache.org/jira/browse/OFBIZ-12818
 Project: OFBiz
  Issue Type: Bug
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing/invoking the 'Acctg Trans Entries PDF' action trigger in 
[https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=8004]
 the user does not get the pdf of the associated accounting transaction. 
Instead following error message is shown:
{code:java}
ERROR MESSAGE

org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request 
[PaymentAcctgTransEntriesPdf]; this request does not exist or cannot be called 
directly.
{code}

the relating uri is: 
https://demo-trunk.ofbiz.apache.org/accounting/control/PaymentAcctgTransEntriesPdf?paymentId=8004



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OFBIZ-12740) webtools entity find does not work for 'Begins With' filter

2023-05-12 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-12740:
-
Affects Version/s: 22.01.01
   Upcoming Branch

> webtools entity find does not work for 'Begins With' filter
> ---
>
> Key: OFBIZ-12740
> URL: https://issues.apache.org/jira/browse/OFBIZ-12740
> Project: OFBiz
>  Issue Type: Bug
>  Components: webtools
>Affects Versions: 18.12.06, 22.01.01, Upcoming Branch
>Reporter: Pierre Smits
>Priority: Major
>
> In demo stable with following uri:
> [OFBiz: Web Tools: Find Values For Entity: StatusItem 
> |https://demo-trunk.ofbiz.apache.org/webtools/control/entity/find/StatusItem?lastUpdatedStamp_fld1_op=opLessThan_op=contains=INV__ic=Y_ic=Y_op=equals_fld0_op=greaterThan_ic=Y_fld0_op=greaterThan_fld0_op=greaterThan_collapsed=true_fld0_op=greaterThan=Y_op=contains_fld1_op=opLessThan_ic=Y_op=contains_ic=Y&_method=GET_fld1_op=opLessThan_op=like_fld1_op=opLessThan_SIZE_1=100_INDEX_1=0]
> The retrieved list should only show records that have a statusTypeId 
> beginning with 'INV_'.
> However, it also shows records that have a statusTypeId beginning with:
>  * INVENTORY_
>  * INVOICE_



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (OFBIZ-12740) webtools entity find does not work for 'Begins With' filter

2023-05-12 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-12740:
-
Description: 
In demo stable with following uri:

[OFBiz: Web Tools: Find Values For Entity: StatusItem 
|https://demo-trunk.ofbiz.apache.org/webtools/control/entity/find/StatusItem?lastUpdatedStamp_fld1_op=opLessThan_op=contains=INV__ic=Y_ic=Y_op=equals_fld0_op=greaterThan_ic=Y_fld0_op=greaterThan_fld0_op=greaterThan_collapsed=true_fld0_op=greaterThan=Y_op=contains_fld1_op=opLessThan_ic=Y_op=contains_ic=Y&_method=GET_fld1_op=opLessThan_op=like_fld1_op=opLessThan_SIZE_1=100_INDEX_1=0]

The retrieved list should only show records that have a statusTypeId beginning 
with 'INV_'.

However, it also shows records that have a statusTypeId beginning with:
 * INVENTORY_
 * INVOICE_

  was:
In demo stable with following uri:

[OFBiz: Web Tools: Find Values For Entity: StatusItem 
(opciones.cl)|https://ofbiz.opciones.cl/webtools/control/entity/find/StatusItem?lastUpdatedStamp_fld1_op=opLessThan_op=contains=INV__ic=Y_ic=Y_op=equals_fld0_op=greaterThan_ic=Y_fld0_op=greaterThan_fld0_op=greaterThan_collapsed=true_fld0_op=greaterThan=Y_op=contains_fld1_op=opLessThan_ic=Y_op=contains_ic=Y&_method=GET_fld1_op=opLessThan_op=like_fld1_op=opLessThan_SIZE_1=100_INDEX_1=0]

The retrieved list should only show records that have a statusTypeId beginning 
with 'INV_'.

However, it also shows records that have a statusTypeId beginning with:
 * INVENTORY_
 * INVOICE_


> webtools entity find does not work for 'Begins With' filter
> ---
>
> Key: OFBIZ-12740
> URL: https://issues.apache.org/jira/browse/OFBIZ-12740
> Project: OFBiz
>  Issue Type: Bug
>  Components: webtools
>Affects Versions: 18.12.06
>Reporter: Pierre Smits
>Priority: Major
>
> In demo stable with following uri:
> [OFBiz: Web Tools: Find Values For Entity: StatusItem 
> |https://demo-trunk.ofbiz.apache.org/webtools/control/entity/find/StatusItem?lastUpdatedStamp_fld1_op=opLessThan_op=contains=INV__ic=Y_ic=Y_op=equals_fld0_op=greaterThan_ic=Y_fld0_op=greaterThan_fld0_op=greaterThan_collapsed=true_fld0_op=greaterThan=Y_op=contains_fld1_op=opLessThan_ic=Y_op=contains_ic=Y&_method=GET_fld1_op=opLessThan_op=like_fld1_op=opLessThan_SIZE_1=100_INDEX_1=0]
> The retrieved list should only show records that have a statusTypeId 
> beginning with 'INV_'.
> However, it also shows records that have a statusTypeId beginning with:
>  * INVENTORY_
>  * INVOICE_



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OFBIZ-12771) Confusing steps to create multiple transactions

2023-03-08 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-12771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697852#comment-17697852
 ] 

Pierre Smits commented on OFBIZ-12771:
--

Hi [~danwatford] 

So, MainActionMenu is missing in the decorator(s) used in GlSetupScreens.xml, 
GlScreens.xml, ReportFinancialSummaryScreens.xml. 

That seems to be easy to fix.

Best regards,
Pierre

> Confusing steps to create multiple transactions
> ---
>
> Key: OFBIZ-12771
> URL: https://issues.apache.org/jira/browse/OFBIZ-12771
> Project: OFBiz
>  Issue Type: Bug
>Affects Versions: 22.01.01
>Reporter: Daniel Watford
>Priority: Minor
> Attachments: image-2023-03-07-14-38-39-731.png, 
> image-2023-03-07-14-39-48-134.png
>
>
> OFBIZ-12447 removed the _Create an Accounting Transaction_ button from the 
> Accounting Transactions screens.
> Compare the same screen on version 18 vs version 22:
> [https://demo-stable.ofbiz.apache.org/accounting/control/FindAcctgTrans?organizationPartyId=Company]
> [https://demo-next.ofbiz.apache.org/accounting/control/FindAcctgTrans?organizationPartyId=Company]
>  
> !image-2023-03-07-14-38-39-731.png|width=512,height=247!
>  
> !image-2023-03-07-14-39-48-134.png|width=464,height=239!
> The button to create a GL Transaction has instead been made available in menu 
> MainActionMenu (AccountingMenus.xml).
> To create a regular transaction (i.e. non-quick transaction) the user must 
> navigate to any of the Accounting application's screens via the app 
> navigation bar EXCEPT for the _Organization GL Settings_ screen. However, 
> clicking the _Create a Gl Transaction_ button in the menu will navigate the 
> user to the Organisation GL Settings screen (sub-application?).
> The user can create their GL Transaction without issue. But if they then wish 
> to enter a second transaction, they must navigate away from the Organisation 
> GL Settings screen so they can once again click on the _Create a Gl 
> Transaction_ button.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12740) webtools entity find does not work for 'Begins With' filter

2023-01-10 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12740:


 Summary: webtools entity find does not work for 'Begins With' 
filter
 Key: OFBIZ-12740
 URL: https://issues.apache.org/jira/browse/OFBIZ-12740
 Project: OFBiz
  Issue Type: Bug
  Components: webtools
Affects Versions: 18.12.06
Reporter: Pierre Smits


In demo stable with following uri:

[OFBiz: Web Tools: Find Values For Entity: StatusItem 
(opciones.cl)|https://ofbiz.opciones.cl/webtools/control/entity/find/StatusItem?lastUpdatedStamp_fld1_op=opLessThan_op=contains=INV__ic=Y_ic=Y_op=equals_fld0_op=greaterThan_ic=Y_fld0_op=greaterThan_fld0_op=greaterThan_collapsed=true_fld0_op=greaterThan=Y_op=contains_fld1_op=opLessThan_ic=Y_op=contains_ic=Y&_method=GET_fld1_op=opLessThan_op=like_fld1_op=opLessThan_SIZE_1=100_INDEX_1=0]

The retrieved list should only show records that have a statusTypeId beginning 
with 'INV_'.

However, it also shows records that have a statusTypeId beginning with:
 * INVENTORY_
 * INVOICE_



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12728) updateProductAverageCostOnReceiveInventory can't expire ProductAverageCost record

2022-12-24 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12728:


 Summary: updateProductAverageCostOnReceiveInventory can't expire 
ProductAverageCost record
 Key: OFBIZ-12728
 URL: https://issues.apache.org/jira/browse/OFBIZ-12728
 Project: OFBiz
  Issue Type: Bug
  Components: product
Reporter: Pierre Smits


Due to a typo the updateProductAverageCostOnReceiveInventory function can't 
expire an old ProductAverageCost record of a product on new inventory receipt.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12720) createInventoryItemVariance should work for serialised product

2022-12-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12720:


 Summary: createInventoryItemVariance should work for serialised 
product
 Key: OFBIZ-12720
 URL: https://issues.apache.org/jira/browse/OFBIZ-12720
 Project: OFBiz
  Issue Type: Improvement
  Components: product/facility
Reporter: Pierre Smits


Currently registering a new InventoryItemVariance record only works for 
non-serialised products. 
However, serialised products can be lost or damaged too, and thus should also 
be registered via the screens that lead to the invocation of the 
createInventoryItemVariance service.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (OFBIZ-12719) ShipmentServices.groovy has wrong parameter value for checkCanChangeShipmentStatusDelivered

2022-12-05 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits closed OFBIZ-12719.

Resolution: Fixed

duplicate

> ShipmentServices.groovy has wrong parameter value for 
> checkCanChangeShipmentStatusDelivered
> ---
>
> Key: OFBIZ-12719
> URL: https://issues.apache.org/jira/browse/OFBIZ-12719
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: 18.12.06
>    Reporter: Pierre Smits
>Priority: Major
>
> on line 732 the parameter shows:
> {code:java}
> parameters.fromStatusId = "SHIPMENT_DEIVERED" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12719) ShipmentServices.groovy has wrong parameter value for checkCanChangeShipmentStatusDelivered

2022-12-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12719:


 Summary: ShipmentServices.groovy has wrong parameter value for 
checkCanChangeShipmentStatusDelivered
 Key: OFBIZ-12719
 URL: https://issues.apache.org/jira/browse/OFBIZ-12719
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: 18.12.06
Reporter: Pierre Smits


on line 732 the parameter shows:
{code:java}
parameters.fromStatusId = "SHIPMENT_DEIVERED" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12718) ShipmentServices.groovy has wrong parameter value for checkCanChangeShipmentStatusDelivered

2022-12-05 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12718:


 Summary: ShipmentServices.groovy has wrong parameter value for 
checkCanChangeShipmentStatusDelivered
 Key: OFBIZ-12718
 URL: https://issues.apache.org/jira/browse/OFBIZ-12718
 Project: OFBiz
  Issue Type: Bug
Affects Versions: 18.12.06
Reporter: Pierre Smits


In line 732 it has
{code:java}
parameters.fromStatusId = "SHIPMENT_DEIVERED" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (OFBIZ-12709) Demo Sites not accessible due to SEC_ERROR_EXPIRED_CERTIFICATE

2022-11-02 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12709:


 Summary: Demo Sites not accessible due to 
SEC_ERROR_EXPIRED_CERTIFICATE
 Key: OFBIZ-12709
 URL: https://issues.apache.org/jira/browse/OFBIZ-12709
 Project: OFBiz
  Issue Type: Bug
Reporter: Pierre Smits






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OFBIZ-12606) Screen projectmgr main is taking long time to load when projects are more

2022-04-28 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529331#comment-17529331
 ] 

Pierre Smits commented on OFBIZ-12606:
--

Also, for the overview shown in the main screen I would say that calling the 
{*}ProjectIsBillable{*}.{*}groovy{*} to generate that overview is irrelevant.

> Screen projectmgr  main is taking long time to load when projects are more
> --
>
> Key: OFBIZ-12606
> URL: https://issues.apache.org/jira/browse/OFBIZ-12606
> Project: OFBiz
>  Issue Type: Bug
>  Components: projectmgr
>Affects Versions: 18.12.05
>Reporter: Balaji Yendamuri
>Priority: Minor
> Fix For: 18.12.06
>
>
> When projects are more than 1000 main screen of projectmgr component is 
> taking very long time  to load
> Currently it is loading all available projects in one shot and there is 
> "{*}ProjectIsBillable{*}.{*}groovy{*}"
> which is calling in row-actions 
> *Solution* : We can use performFind service  to increase performance in this 
> screen



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Commented] (OFBIZ-12606) Screen projectmgr main is taking long time to load when projects are more

2022-04-28 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529326#comment-17529326
 ] 

Pierre Smits commented on OFBIZ-12606:
--

With a huge number of projects records in the WorkEffort table, I can imagine 
that a lot of those records have the status PRJ_CANCELED or PRJ_CLOSED. 
Therefore it seems a good thing to only show the projects with status 
PRJ_ACTIVE in the main screen, as there is already a screen to search and find 
projects.

> Screen projectmgr  main is taking long time to load when projects are more
> --
>
> Key: OFBIZ-12606
> URL: https://issues.apache.org/jira/browse/OFBIZ-12606
> Project: OFBiz
>  Issue Type: Bug
>  Components: projectmgr
>Affects Versions: 18.12.05
>Reporter: Balaji Yendamuri
>Priority: Minor
> Fix For: 18.12.06
>
>
> When projects are more than 1000 main screen of projectmgr component is 
> taking very long time  to load
> Currently it is loading all available projects in one shot and there is 
> "{*}ProjectIsBillable{*}.{*}groovy{*}"
> which is calling in row-actions 
> *Solution* : We can use performFind service  to increase performance in this 
> screen



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Commented] (OFBIZ-12568) In Helveticus theme the product assoc screen is pretty unusable

2022-02-09 Thread Pierre Smits (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-12568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489515#comment-17489515
 ] 

Pierre Smits commented on OFBIZ-12568:
--

This is a duplicate of OFBIZ-12398.

> In Helveticus theme the product assoc screen is pretty unusable
> ---
>
> Key: OFBIZ-12568
> URL: https://issues.apache.org/jira/browse/OFBIZ-12568
> Project: OFBiz
>  Issue Type: Bug
>  Components: themes/helveticus
>Affects Versions: 18.12.06, 22.01.01
>Reporter: Jacques Le Roux
>Priority: Major
>
> It's easily reproductible when going to eg 
> catalog/control/EditProductAssoc?productId=GZ-1000
> Other themes are OK



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (OFBIZ-12569) EditTrackingCode screen - duplicate action trigger

2022-02-09 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12569:


 Summary: EditTrackingCode screen - duplicate action trigger
 Key: OFBIZ-12569
 URL: https://issues.apache.org/jira/browse/OFBIZ-12569
 Project: OFBiz
  Issue Type: Bug
  Components: marketing/marketing
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
https://localhost:8443/marketing/control/EditTrackingCode?trackingCodeId=9000 
the action trigger "Create Tracing Code" is duplicated.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OFBIZ-12565) Billing Account Payments - VIEW permissions

2022-02-09 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-12565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits reassigned OFBIZ-12565:


Assignee: Pierre Smits

> Billing Account Payments - VIEW permissions
> ---
>
> Key: OFBIZ-12565
> URL: https://issues.apache.org/jira/browse/OFBIZ-12565
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Upcoming Branch
>Reporter: Pierre Smits
>    Assignee: Pierre Smits
>Priority: Major
>  Labels: billing-account, permissions, trust, user-experience
>
> When accessing 
> [https://localhost:8443/accounting/control/BillingAccountPayments?billingAccountId=9010]
>  as a user with only VIEW permissions (e.g. userid=auditor), the screen shows 
> a form to create a payment.
> This should not be visible to such a user as it leads to a undesired effect 
> and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


Re: TrackingCode siteId

2022-02-09 Thread Pierre Smits
Guten Morgen Ingo,

The field definition appears in marketing-entitymodel.xml in the entity
definition "TrackingCodeOrder" and in entity definition
"TrackingCodeOrderReturn". In both as a long-varchar type.
In file TrackingCodeEvents.java, it appears at line 266 and line 554.

Please raise an issue in our JIRA if you feel it needs to be addressed.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory <https://directory.apache.org>, PMC Member*

Anyone could have been you, whereas I've always been anyone.


On Wed, Feb 9, 2022 at 10:56 AM Ingo Wolfmayr 
wrote:

> Hi everybody,
>
>
>
> I am testing the "Tracking Code" part of the marketing module and was
> wondering where the "siteId" comes from. I get a null pointer exeption when
> calling a page with a tracking code.
>
>
>
> Caused by: java.lang.NullPointerException
>
> at java.net.URLEncoder.encode(URLEncoder.java:224) ~[?:?]
>
> at java.net.URLEncoder.encode(URLEncoder.java:196) ~[?:?]
>
> at
> org.apache.ofbiz.marketing.tracking.TrackingCodeEvents.processTrackingCode(TrackingCodeEvents.java:267)
> ~[main/:?]
>
> at
> org.apache.ofbiz.marketing.tracking.TrackingCodeEvents.checkPartnerTrackingCodeUrlParam(TrackingCodeEvents.java:175)
> ~[main/:?]
>
>
>
> I looked into the ofbiz code but could not find the place where it is set.
>
>
>
> Best regards,
>
> Ingo
>
>
>
> Mag. (FH) Ingo Wolfmayr
>
> *Wolfix Solutions*
>
> Gänsgasse 14
>
> A-5282 Ranshofen
>
>
>
> Tel.: +43 (0) 664 2549626
>
> Web: https://www.wolfix.at
>
> Xing: https://www.xing.com/profile/Ingo_Wolfmayr/
>
>
>
> [image: emailsignatur]
>
>
>
>
>


[jira] [Created] (OFBIZ-12567) FinAccount Screen shows create trigger to user with VIEW permission

2022-02-08 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12567:


 Summary: FinAccount Screen shows create trigger to user with VIEW 
permission
 Key: OFBIZ-12567
 URL: https://issues.apache.org/jira/browse/OFBIZ-12567
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://localhost:8443/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING]
 as a user with only VIEW permissions (e.g. userid=auditor) the screen shows a 
action trigger to create something. 

This should not be visible to such a user as it leads to a undesired effect and 
diminished user experience.

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (OFBIZ-12566) Screen FinAccountMain shows create trigger to user with VIEW permissions

2022-02-08 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12566:


 Summary: Screen FinAccountMain shows create trigger to user with 
VIEW permissions
 Key: OFBIZ-12566
 URL: https://issues.apache.org/jira/browse/OFBIZ-12566
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing [https://localhost:8443/accounting/control/FinAccountMain] as a 
user with only ViEW permissions (e.g. userId=auditor) an action trigger to 
create something is shown. 

This should not be visible to such a user as it leads to a undesired effect and 
diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (OFBIZ-12565) Billing Account Payments - VIEW permissions

2022-02-08 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12565:


 Summary: Billing Account Payments - VIEW permissions
 Key: OFBIZ-12565
 URL: https://issues.apache.org/jira/browse/OFBIZ-12565
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://localhost:8443/accounting/control/BillingAccountPayments?billingAccountId=9010]
 as a user with only VIEW permissions (e.g. userid=auditor), the screen shows a 
form to create a payment.
This should not be visible to such a user as it leads to a undesired effect and 
diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (OFBIZ-12564) Edit Billing Account screen shows create trigger to user with VIEW permission

2022-02-08 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12564:


 Summary: Edit Billing Account screen shows create trigger to user 
with VIEW permission
 Key: OFBIZ-12564
 URL: https://issues.apache.org/jira/browse/OFBIZ-12564
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing 
[https://localhost:8443/accounting/control/EditBillingAccount?billingAccountId=9010]
 as a user  with only VIEW permissions (e.g. userid=auditor), the screen shows 
an action trigger to create something.. This should not be visible to such a 
user as it leads to a undesired effect and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (OFBIZ-12563) Find Billing Account screen shows 'create' trigger to user with VIEW permission

2022-02-08 Thread Pierre Smits (Jira)
Pierre Smits created OFBIZ-12563:


 Summary: Find Billing Account screen shows 'create' trigger to 
user with VIEW permission
 Key: OFBIZ-12563
 URL: https://issues.apache.org/jira/browse/OFBIZ-12563
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: Upcoming Branch
Reporter: Pierre Smits


When accessing  [https://localhost:8443/accounting/control/FindBillingAccount] 
as a user with only VIEW permissions (e.g. userId=auditor, the action trigger 
to create something is shown. This should not be visible to such a user as it 
leads to a undesired effect and diminished user experience.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


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