[jira] [Updated] (DIRSTUDIO-709) Add support for password policy request and response controls
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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.
[
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
[ 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
[ 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
[ 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
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
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
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
[ 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
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
[
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)
[ 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
[ 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
[ 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
[
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
[ 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
[
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
[ 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
[
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
[ 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
[
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
[ 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
[ 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
[
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
[ 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!
[
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
[ 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
[ 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
[
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
[ 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
[ 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.
[ 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
[
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
[
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
[
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
[
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
[ 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
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
[ 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
[ 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.
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
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
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
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
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
[
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
[
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
[ 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
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
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
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
[ 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
[ 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
[ 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
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
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
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
[
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
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
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
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
[
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
[
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
[ 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
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
[ 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
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
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
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
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
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
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)
[jira] [Created] (OFBIZ-12562) Search result FindPayment Group shows 'Cancel trigger to user with view permission
Pierre Smits created OFBIZ-12562: Summary: Search result FindPayment Group shows 'Cancel trigger to user with view permission Key: OFBIZ-12562 URL: https://issues.apache.org/jira/browse/OFBIZ-12562 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits When accessing [https://localhost:8443/accounting/control/FindPaymentGroup] as a user with only VIEW permissions (e.g. userId=auditor), the overview of payments found shows an action trigger to cancel a payment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12561) Payment Find screen shows unnecessary 'find' trigger
Pierre Smits created OFBIZ-12561: Summary: Payment Find screen shows unnecessary 'find' trigger Key: OFBIZ-12561 URL: https://issues.apache.org/jira/browse/OFBIZ-12561 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits When accessing [https://localhost:8443/accounting/control/findPayments] a trigger is shown to access the Payment Find screen. This is redundant. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12560) Party Main: duplicate action trigger (Person/Group)
Pierre Smits created OFBIZ-12560: Summary: Party Main: duplicate action trigger (Person/Group) Key: OFBIZ-12560 URL: https://issues.apache.org/jira/browse/OFBIZ-12560 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits When accessing [https://localhost:8443/partymgr/control/main] the screen shows duplicate action triggers for the creation of a new party of type=PERSON or of type=PARTYGROUP. These action triggers come from the MainActionMenu for the a component, and from the 'CreateNewParty' menu. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12559) GlSetupScreens.xml - MainActionMenu not shown
Pierre Smits created OFBIZ-12559: Summary: GlSetupScreens.xml - MainActionMenu not shown Key: OFBIZ-12559 URL: https://issues.apache.org/jira/browse/OFBIZ-12559 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits The MainActionMenu of the Accounting component is intended to provide the users with CREATE permissions a direct way to create the main objects of the Accounting components (Gl transaction, invoice, payment), instead of - as such a user - have to go through multiple screens to get to the action trigger to create such objects. The MainActionMenu is applied in various decorator screens. It is, however, not applied in the GlSetupScreen.xml file. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: [jira] [Commented] (OFBIZ-12489) Product Prices - VIEW permissions
My thanks goes out to those members of the OFBiz PMC who recognised (and
agreed with me) that volunteers feeling attacked ("trolled") by feedback of
PMC and ASF Member Michael Brohl is detrimental to the health of the
project,.
His behaviour, as displayed in various comments on tickets and pull
requests over the past two months, has caused engagement of and healthy,
constructive discussions between collaborating volunteers to not only
decline, but also swing like a pendulum. Making it more difficult for
collaborating contributors to come to conclusions and consensus to move
forward.
Thanks for recognising, like me, that the heated and fruitless debates
caused by this behaviour is a waste of my and fellow contributors' precious
time.
I trust that talks within the PMC has shown Michael the error of his ways,
and can learn from this.. And I hope that, now this has been addressed, the
community can come back together and get healed. Leading to more happy
collaborations working towards a better community and its works with each
of the engaging interactions.
I also thank the members of the ASF who stepped up and advised the members
of the OFBiz PMC, regarding the inappropriate behaviour of Michael Brohl.
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 Mon, Feb 7, 2022 at 9:06 PM Jacopo Cappellato <
jacopo.cappell...@gmail.com> wrote:
> Pierre,
>
> The OFBiz PMC has reviewed your complaints and has received some advice
> from various ASF members: with this response we are implementing some of
> those.
> The PMC considers troublesome the fact that you feel attacked ("trolled")
> by the feedback you receive by Michael (and possibly others) and that you
> consider the feedback being "inappropriate", because it prevents any
> possibility to discuss your contributions in a constructive manner, it
> leads to heated and fruitless debates that may be unhealthy for the OFBiz
> community and a waste of time for its contributors.
>
> The PMC has thus decided to ask the project's volunteers (PMC members,
> committers and contributors) to put "on hold" or reject or disregard any
> of your contributions, such as code, documentation, mailing list
> discussions
> etc. and close Jira issues and pull requests that are not straightforward
> and require further interactions/discussions with you before they can be
> approved or accepted.
>
> On behalf of the Apache OFBiz PMC,
>
> Jacopo
>
>
> On Tue, Jan 25, 2022 at 2:01 AM Pierre Smits
> wrote:
>
>> Michael,
>>
>> I told you before in (other) tickets to stop trolling me through your
>> complaints in the tickets I am working on. You continue to do this.
>> Your remarks about you not committing the code contributions of
>> unprivileged contributors are totally inappropriate. Not appropriate in
>> ticket comments, nor in the mailing lists of the project. Nobody is
>> strong-arming you to commit or merge improvements. Nobody is expecting you
>> ever will.
>> Stop trying to pressure fellow contributors, collaborating to improve
>> OFBiz, to follow your dictate by your attempt to frame a narrative that
>> there is an agreement about how contributors are to contribute what, where
>> and when.
>> Such narrative is solely intended to dictate the direction of the project
>> for your self serving purposes, resulting in alienating fellow
>> contributors
>> from collaborating in the OFBiz project to get improvements into its
>> repositories.
>>
>> There has never been such an agreement on how, what, where and when to
>> contribute in the OFBiz community. Nor on the specific subject of what the
>> correct translation label that is to be used in OFBiz screens and forms.
>> No discussion on that latter subject has ever been started on the dev
>> mailing list, nor is there any series of postings on that list that could
>> lead to someone being able to claim that a kind of consensus could be
>> derived from such a thread.
>>
>> It appears, IMO, that you don't want what is for the good of the public
>> through the deliverables of the OFBiz project.
>> Your business needs and goals are not the concerns of the project, nor the
>> concerns of the contributors not paid by you(r company).
>> You keep your Ecomify rules re OFBiz to yourself and for your employees,
>> instead of presenting them as rules (or agreements) of the project. In
>> this
>> project there are no such 'contribution' rules.
&g
Re: [GitHub] [ofbiz-framework] mbrohl commented on pull request #496: Improved: List and Grid (OFBIZ-11345)
You don't get the point, Michael. You DON'T get to dictate what is being contributed to the project for the public good. Should not be so hard to understand for a member of a project's PMC and the ASF. 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 Mon, Feb 7, 2022 at 5:05 PM Michael Brohl wrote: > You don't get the point, Pierre. > > You are actively REMOVING elements others have contributed and put > effort in. > > Shouldn't be too hard to understand. > > Michael > > > Am 07.02.22 um 16:52 schrieb Pierre Smits: > > *Re: Other contributors have taken their time to structure the code into > > readable blocks and comment them.* > > Other contributors have taken their time to provide clean code without > [...] > > >
Re: [GitHub] [ofbiz-framework] mbrohl commented on pull request #496: Improved: List and Grid (OFBIZ-11345)
*Re: Other contributors have taken their time to structure the code into readable blocks and comment them.* Other contributors have taken their time to provide clean code without caring for readable blocks or commenting those, and their contributions also went into the codebase. Other contributors have collaborated to get to cleaner (code) files, and the result of these collaborations also went into the codebase. *Re: If you want the functional changes go in, either stop removing those elements or, if that's the problem, learn how to configure your XML Editor to leave blank lines and comments as-is* Again? Extortion of compliance to* "your"* rules? Trying that 'approach' again? You, again, try to dictate what can be contributed, when, how and by whom. I will not comport with your dictatorship. Stop being an embarrassment to the project and the ASF. These actions of yours result in nothing more than a hostile environment that chases (potential) contributors away and hurts collaboration between contributors. Re: https://github.com/apache/ofbiz-framework/pull/496#issuecomment-1031457572 The changes committed in this pull request are in line with guidelines and best practices established over the course of the project under the wings of the ASF, which were applied on merged pull request as recent as 7 days ago. If you want the guidelines changed, you are welcome to start a discussion in dev@. You can **NOT** unilaterally decide what will and will not be merged by other volunteers. That is **dictatorship**! 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 Mon, Feb 7, 2022 at 4:05 PM GitBox wrote: > > mbrohl commented on pull request #496: > URL: > https://github.com/apache/ofbiz-framework/pull/496#issuecomment-1031566131 > > >Other contributors have taken their time to structure the code into > readable blocks and comment them. >You are removing this work and make the code look worse than before at > those locations, therefore it cannot be accepted. > >If you want the functional changes go in, either stop removing those > elements or, if that's the problem, learn how to configure your XML Editor > to leave blank lines and comments as-is. > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > >
Re: [GitHub] [ofbiz-framework] mbrohl commented on pull request #501: Improved: List and Grid (OFBIZ-11345)
It is not about that anymore, is it now? 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 Sun, Feb 6, 2022 at 1:06 PM GitBox wrote: > > mbrohl commented on pull request #501: > URL: > https://github.com/apache/ofbiz-framework/pull/501#issuecomment-1030819296 > > >This again contains changes actively removing separating blank lines, > which makes the files less readable. >If you are really interested in getting the functional changes into the > codebase, why do you still introduce those changes and mix it up with the > functional changes? > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > >
[jira] [Commented] (OFBIZ-12524) Production Run - VIEW permissions
[
https://issues.apache.org/jira/browse/OFBIZ-12524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487478#comment-17487478
]
Pierre Smits commented on OFBIZ-12524:
--
[GitHub Pull Request #475|https://github.com/apache/ofbiz-framework/pull/475]
now needs to be reworked. Caused by out-of-sequence commit/merge of
[{{{}418d6e0{}}}#diff-1fbd717a3a3a1f3c301b977057d68e3748c1a233373c362b8be4c0a3dd070aa6|https://github.com/apache/ofbiz-framework/commit/418d6e03d45c3647f96dbc1f7630b348a60d11f1#diff-1fbd717a3a3a1f3c301b977057d68e3748c1a233373c362b8be4c0a3dd070aa6]
> Production Run - VIEW permissions
> -
>
> Key: OFBIZ-12524
> URL: https://issues.apache.org/jira/browse/OFBIZ-12524
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
>Affects Versions: Upcoming Branch
>Reporter: Pierre Smits
> Assignee: Pierre Smits
>Priority: Major
> Labels: permissions, productionrun, trust, usability, ux
>
> Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo
> with userId = auditor, accessing the Production run screen, sees editable
> fields and/or triggers (to requests) reserved for users with 'CREATE' or
> 'UPDATE' permissions.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: [ofbiz-framework] branch trunk updated: Fixed: Manufacturing Jobshop find screen by default does not show all production runs (OFBIZ-12550)
Due to this merge the PR regarding OFBIZ-12524 (
https://github.com/apache/ofbiz-framework/pull/475 of January 23rd) is now
useless due to merge conflicts, causing work to be redone.
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 Tue, Feb 1, 2022 at 8:59 AM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> jleroux pushed a commit to branch trunk
> in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
>
>
> The following commit(s) were added to refs/heads/trunk by this push:
> new 418d6e0 Fixed: Manufacturing Jobshop find screen by default does
> not show all production runs (OFBIZ-12550)
> 418d6e0 is described below
>
> commit 418d6e03d45c3647f96dbc1f7630b348a60d11f1
> Author: Jacques Le Roux
> AuthorDate: Tue Feb 1 08:57:29 2022 +0100
>
> Fixed: Manufacturing Jobshop find screen by default does not show all
> production runs (OFBIZ-12550)
>
> The manufacturing jobshop find screen has the seach date initialized
> to nowdate.
> if one wants to see all production runs, one has to clear the date
> which should
> be empty initially
>
> The same problem exists on the MRP log find where the date is filled
> by default.
>
> Thanks: Hans for report and patches
> ---
> applications/manufacturing/template/mrp/FindInventoryEventPlan.ftl |
> 2 +-
> applications/manufacturing/widget/manufacturing/ProductionRunForms.xml |
> 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
> a/applications/manufacturing/template/mrp/FindInventoryEventPlan.ftl
> b/applications/manufacturing/template/mrp/FindInventoryEventPlan.ftl
> index 825afc1..d2ed694 100644
> --- a/applications/manufacturing/template/mrp/FindInventoryEventPlan.ftl
> +++ b/applications/manufacturing/template/mrp/FindInventoryEventPlan.ftl
> @@ -70,7 +70,7 @@ function lookupInventory() {
> class="label">${uiLabelMap.CommonFromDate}
>
>
> - <@htmlTemplate.renderDateTimeField name="eventDate"
> event="" action="" className="" alert="" title="Format: -MM-dd
> HH:mm:ss.SSS" value="${requestParameters.eventDate!nowTimestamp}" size="25"
> maxlength="30" id="fromDate_2" dateType="date" shortDateInput=false
> timeDropdownParamName="" defaultDateTimeString="" localizedIconTitle=""
> timeDropdown="" timeHourName="" classString="" hour1="" hour2=""
> timeMinutesName="" minutes="" isTwelveHour="" ampmName="" amSelected=" [...]
> + <@htmlTemplate.renderDateTimeField name="eventDate"
> event="" action="" className="" alert="" title="Format: -MM-dd
> HH:mm:ss.SSS" value="" size="25" maxlength="30" id="fromDate_2"
> dateType="date" shortDateInput=false timeDropdownParamName=""
> defaultDateTimeString="" localizedIconTitle="" timeDropdown=""
> timeHourName="" classString="" hour1="" hour2="" timeMinutesName=""
> minutes="" isTwelveHour="" ampmName="" amSelected="" pmSelected=""
> compositeType="" formName=""/>
>
>
>
> diff --git
> a/applications/manufacturing/widget/manufacturing/ProductionRunForms.xml
> b/applications/manufacturing/widget/manufacturing/ProductionRunForms.xml
> index c5674b8..73b42b6 100644
> ---
> a/applications/manufacturing/widget/manufacturing/ProductionRunForms.xml
> +++
> b/applications/manufacturing/widget/manufacturing/ProductionRunForms.xml
> @@ -80,7 +80,7 @@ under the License.
>
> title="${uiLabelMap.ProductProductId}"> target-form-name="LookupProduct"/>
> title="${uiLabelMap.ManufacturingProductionRunName}">
> - title="${uiLabelMap.ManufacturingStartDate}"> default-value="${nowTimestamp}"/>
> + title="${uiLabelMap.ManufacturingStartDate}">
>
>
> key-field-name="facilityId" description="${facilityName} [${facilityId}]">
>
Re: [jira] [Commented] (OFBIZ-11948) Remote Code Execution (File Upload) Vulnerability
Hi Jacques,
in a posting above, you stated:
* Adds "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, Feb 4, 2022 at 2:06 PM Jacques Le Roux
wrote:
> Hi Pierre,
>
> How is your question related?
>
> Le 04/02/2022 à 12:53, Pierre Smits a écrit :
> > Hi Jacques,
> >
> > Wasn't there PHP code in the scrum application/ component to work with a
> > git repository?
> >
> > Or was that Python?
> >
> >
> > Op vr 4 feb. 2022 12:32 schreef ASF subversion and git services (Jira) <
> > j...@apache.org>:
> >
> >> [
> >>
> https://issues.apache.org/jira/browse/OFBIZ-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487028#comment-17487028
> >> ]
> >>
> >> ASF subversion and git services commented on OFBIZ-11948:
> >> -
> >>
> >> Commit b0b02034eecf8d18ac7ea12f34469ec511269fa0 in ofbiz-framework's
> >> branch refs/heads/trunk from Jacques Le Roux
> >> [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=b0b0203 ]
> >>
> >> Fixed: Remote Code Execution (File Upload) Vulnerability (OFBIZ-11948)
> >>
> >> Lion Tree has reported us that
> >> "CVE-2020-1938 is not fully fixed".
> >>
> >> Though it was fixed by OFBIZ-11407, it still possible for an
> authenticated
> >> user
> >> to upload a webshell included in an image using one of the upload
> >> possibilities
> >> in OFBiz. That is not new and covered by OFBIZ-12080 "Secure the
> uploads",
> >> but
> >> was still incomplete.
> >>
> >> This enforces the secured uploads by
> >> * checking in SecuredUpload::isValidImageFile that a webshell is not
> >> embedded in
> >> an image.
> >> * Keeping only "<%" as a denied token for JSP webshells, instead of
> >> currently
> >> "<%@ page"
> >> * Adds "application/text/x-ruby" to SecuredUpload::isExecutable
> >>
> >> Also
> >> * Adds " >> it's often installed on servers.
> >> * Removes "import=\"java" and "runtime.getruntime().exec(". They are no
> >> longer useful since "<%" and " >> * Remove php token since I'll put " >> * Adds "#!", rather than adding other shebangs like perl,python and ruby
> >>
> >> This will make deniedWebShellTokens more understandable.
> >>
> >> But I'm conscious that despite SecuredUpload::isExecutableI I still
> need to
> >> better handle encoded webshells. I'll do that soon in a second approach.
> >>
> >> I'll also certainly more prune PHP related tokens.
> >>
> >> Thanks: Lion Tree for report
> >>
> >>
> >>> Remote Code Execution (File Upload) Vulnerability
> >>> -
> >>>
> >>> Key: OFBIZ-11948
> >>> URL:
> https://issues.apache.org/jira/browse/OFBIZ-11948
> >>> Project: OFBiz
> >>> Issue Type: Sub-task
> >>> Components: product/catalog
> >>> Affects Versions: Trunk, 17.12.04, 18.12.01
> >>> Reporter: Jacques Le Roux
> >>> Assignee: Jacques Le Roux
> >>> Priority: Major
> >>> Fix For: 17.12.05, 18.12.01
> >>>
> >>>
> >>> Harshit Shukla harshit.sh...@gmail.com reported this RCE vulnerability
> >> to the OFBiz security team, and we thank him for that.
> >>> I'll later quote here his email message when the vulnerability will be
> >> fixed. It's a post-auth vulnerability so we did not ask for a CVE.
> >>
> >>
> >>
> >> --
> >> This message was sent by Atlassian Jira
> >> (v8.20.1#820001)
> >>
>
Re: [jira] [Commented] (OFBIZ-11948) Remote Code Execution (File Upload) Vulnerability
Hi Jacques,
Wasn't there PHP code in the scrum application/ component to work with a
git repository?
Or was that Python?
Op vr 4 feb. 2022 12:32 schreef ASF subversion and git services (Jira) <
j...@apache.org>:
>
> [
> https://issues.apache.org/jira/browse/OFBIZ-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487028#comment-17487028
> ]
>
> ASF subversion and git services commented on OFBIZ-11948:
> -
>
> Commit b0b02034eecf8d18ac7ea12f34469ec511269fa0 in ofbiz-framework's
> branch refs/heads/trunk from Jacques Le Roux
> [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=b0b0203 ]
>
> Fixed: Remote Code Execution (File Upload) Vulnerability (OFBIZ-11948)
>
> Lion Tree has reported us that
> "CVE-2020-1938 is not fully fixed".
>
> Though it was fixed by OFBIZ-11407, it still possible for an authenticated
> user
> to upload a webshell included in an image using one of the upload
> possibilities
> in OFBiz. That is not new and covered by OFBIZ-12080 "Secure the uploads",
> but
> was still incomplete.
>
> This enforces the secured uploads by
> * checking in SecuredUpload::isValidImageFile that a webshell is not
> embedded in
> an image.
> * Keeping only "<%" as a denied token for JSP webshells, instead of
> currently
> "<%@ page"
> * Adds "application/text/x-ruby" to SecuredUpload::isExecutable
>
> Also
> * Adds " it's often installed on servers.
> * Removes "import=\"java" and "runtime.getruntime().exec(". They are no
> longer useful since "<%" and " * Remove php token since I'll put " * Adds "#!", rather than adding other shebangs like perl,python and ruby
>
> This will make deniedWebShellTokens more understandable.
>
> But I'm conscious that despite SecuredUpload::isExecutableI I still need to
> better handle encoded webshells. I'll do that soon in a second approach.
>
> I'll also certainly more prune PHP related tokens.
>
> Thanks: Lion Tree for report
>
>
> > Remote Code Execution (File Upload) Vulnerability
> > -
> >
> > Key: OFBIZ-11948
> > URL: https://issues.apache.org/jira/browse/OFBIZ-11948
> > Project: OFBiz
> > Issue Type: Sub-task
> > Components: product/catalog
> >Affects Versions: Trunk, 17.12.04, 18.12.01
> >Reporter: Jacques Le Roux
> >Assignee: Jacques Le Roux
> >Priority: Major
> > Fix For: 17.12.05, 18.12.01
> >
> >
> > Harshit Shukla harshit.sh...@gmail.com reported this RCE vulnerability
> to the OFBiz security team, and we thank him for that.
> > I'll later quote here his email message when the vulnerability will be
> fixed. It's a post-auth vulnerability so we did not ask for a CVE.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.20.1#820001)
>
Re: [GitHub] [ofbiz-framework] mbrohl commented on pull request #498: Improved: WorkEffort - MainActionMenu (OFBIZ-12557)
Indeed, Michael. That was what you said in comments regarding: 1. https://github.com/apache/ofbiz-framework/pull/481 2. https://github.com/apache/ofbiz-framework/pull/482 3. https://github.com/apache/ofbiz-framework/pull/483 and now again in https://github.com/apache/ofbiz-framework/pull/498 What is this RULE of yours that fellow volunteering contributors MUST comply with in order to have their improvements go into the codebase: Is it single line spacing, *or* Is ig double line spacing? It must surely feel very frustrating and annoying (even maybe painful?) when YOU look at code in the OFBiz repositories and the majority of that code not having the single or double line spacing that you want. How unfortunate that all those contributors of code improvements over the past 15 years of this project's existence (including you, contributing for as long as that, as your claimed elsewhere) violated that RULE of yours (that you brought forward just 11 days ago). If the code of OFBiz (and improvements thereon) give you so much difficulties to read, maybe there are some helpful tools available for you to continue to bring your valuable contributions to improve this project and its works? Or maybe it is time to call it quits? 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 Thu, Feb 3, 2022 at 8:12 PM GitBox wrote: > > mbrohl commented on pull request #498: > URL: > https://github.com/apache/ofbiz-framework/pull/498#issuecomment-1029313372 > > >As said before, the removal of blank lines between sections makes the > files harder to read. > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: notifications-unsubscr...@ofbiz.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > >
[jira] [Created] (OFBIZ-12557) WorkEffort - MainActionMenu
Pierre Smits created OFBIZ-12557: Summary: WorkEffort - MainActionMenu Key: OFBIZ-12557 URL: https://issues.apache.org/jira/browse/OFBIZ-12557 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently the create buttons for the main objects of the work effort are located within the find and other widgets/templates of those objects. In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12484) Project - MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12484: - Labels: menus refactoring usability user-experience (was: menus refactoring usability ux) > Project - MainActionMenu > > > Key: OFBIZ-12484 > URL: https://issues.apache.org/jira/browse/OFBIZ-12484 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability, user-experience > > Currently the create buttons for the main objects of the project mgt plugin > are located within the find and other widgets/templates of those objects. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12556) Request "createWorkEffortPartyAssign" generates an error
Pierre Smits created OFBIZ-12556:
Summary: Request "createWorkEffortPartyAssign" generates an error
Key: OFBIZ-12556
URL: https://issues.apache.org/jira/browse/OFBIZ-12556
Project: OFBiz
Issue Type: Bug
Components: projectmgr
Affects Versions: Upcoming Branch
Reporter: Pierre Smits
The request "createWorkEffortPartyAssign" is called after submitting the form
"AddWorkEffortPartyAssign", when the user wants to add a party to a project.
The resulting error is:
{code:java}
|E| Error in request handler:
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[createWorkEffortPartyAssign]; this request does not exist or cannot be called
directly.
at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:407)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.handle(ControlServlet.java:231)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doPost(ControlServlet.java:81)
[ofbiz.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:681)
[tomcat-servlet-api-9.0.58.jar:4.0.FR]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
[tomcat-servlet-api-9.0.58.jar:4.0.FR]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
[tomcat-embed-websocket-9.0.41.jar:9.0.41]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.ofbiz.webapp.control.SameSiteFilter.doFilter(SameSiteFilter.java:45)
[ofbiz.jar:?]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:188)
[ofbiz.jar:?]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
[ofbiz.jar:?]
at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:57)
[tomcat-servlet-api-9.0.58.jar:4.0.FR]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71)
[log4j-web-2.17.1.jar:2.17.1]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359)
[tomcat-catalina-9.0.58.jar:9.0.58]
at
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
[tomcat-coyote-9.0.58.jar:9.0.58]
at
org.apache.coyote.
[jira] [Commented] (OFBIZ-12534) Comments on Commits in Github must go to a mailing list of the project
[ https://issues.apache.org/jira/browse/OFBIZ-12534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486333#comment-17486333 ] Pierre Smits commented on OFBIZ-12534: -- Hi Jacques, You probably read the same as I did, leading to this inevitable conclusion: INFRA (in collaboration with the Github organisation) is currently unable to ensure, that GitHub services (available to contributors (of any Apache project) forward a comment posted on a commit there to a project's mailing list. It seems to me, that INFRA and Github could have talks about this to address this ASF wide issue. > Comments on Commits in Github must go to a mailing list of the project > -- > > Key: OFBIZ-12534 > URL: https://issues.apache.org/jira/browse/OFBIZ-12534 > Project: OFBiz > Issue Type: Improvement > Components: GitHub > Reporter: Pierre Smits >Priority: Major > > Currently, when a contributor posts a comment to a (merged) commit in Github, > this comment does not end up in one of the mailing lists of the project, > whereas comments to pull request in Github do. > This not forwarding/sending of a comment to a mailing list of the project > should not happen, as per one of the ASF mottos: if it didn't land in a > mailing list, it didn't happen. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: [ofbiz-framework] branch trunk updated: Improved: no functional change, labels improvements
I'll not apologize either for following guidelines and practices established, having the consensus. Op do 3 feb. 2022 09:47 schreef Jacques Le Roux < jacques.le.r...@les7arts.com>: > And again (again, again, again) all depend on context. Here it's quite > obvious that there are no labels changes, only tabs replaced by spaces. > > I though agree that it should have been another commit, just that I missed > that because I automate (too?) much things. > > I'll not apologize :p > > Le 03/02/2022 à 09:27, Michael Brohl a écrit : > > I did not confirm that. > > > > My response was targeted to the wrong assumptions that the changes were > only removes/same additions and the result of an unclean state of the > > working copy. > > > > It is generally better to separate formatting / cleanup from real > changes, which I did not mention here. For pull requests and patches, > separation > > helps the reviewer to see through and makes it possible to only merge > commits which contain wanted changes. > > > > Not sure if this warrants a mail to dev, at least you were the one > lately who complained to not play the blame game [1]. > > > > Michael > > > > [1] https://lists.apache.org/thread/93ptk5nfrf2pjfwnl6ovm0lc6l42yb85 > > > > > > Am 03.02.22 um 08:18 schrieb Pierre Smits: > >> Good to see that the two of you confirm that cleanup can be combined > with > >> other improvements . > >> > >> Op do 3 feb. 2022 07:15 schreef Jacques Le Roux < > >> jacques.le.r...@les7arts.com>: > >> > >>> Yep, thanks Michael, > >>> > >>> Jacques > >>> > >>> Le 02/02/2022 à 23:33, Michael Brohl a écrit : > >>>> If I see it right, he has corrected wrong indentations. Nothing wrong > >>> with that... > >>>> Michael > >>>> > >>>> > >>>> Am 02.02.22 um 18:00 schrieb Pierre Smits: > >>>>> Hi Jacques, > >>>>> > >>>>> With this commit 8a9596be849f6709cb17c24a598c4862e8df867c you deleted > >>> and > >>>>> reinserted a lot of german translations (without any changes in the > >>>>> translation at first glance). > >>>>> > >>>>> Were these necessary, or an unfortunate combination of circumstances > >>>>> leading to you not working with a clean dev branch? It is a pity this > >>>>> happened. Luckily, the impact is trivial. But people tend to get > >>> confused > >>>>> by this, and it could lead to complaints or heated arguments. > >>>>> > >>>>> Can you be a bit more careful next time around? > >>>>> > >>>>> Atentamente > >>>>> 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 Sun, Jan 16, 2022 at 8:52 AM wrote: > >>>>> > >>>>>> This is an automated email from the ASF dual-hosted git repository. > >>>>>> > >>>>>> jleroux pushed a commit to branch trunk > >>>>>> in repository > https://gitbox.apache.org/repos/asf/ofbiz-framework.git > >>>>>> > >>>>>> > >>>>>> The following commit(s) were added to refs/heads/trunk by this push: > >>>>>>new 8a9596b Improved: no functional change, labels > improvements > >>>>>> 8a9596b is described below > >>>>>> > >>>>>> commit 8a9596be849f6709cb17c24a598c4862e8df867c > >>>>>> Author: Jacques Le Roux > >>>>>> AuthorDate: Sun Jan 16 08:51:03 2022 +0100 > >>>>>> > >>>>>> Improved: no functional change, labels improvements > >>>>>> > >>>>>> In French, and maybe other languages, there is not only one > word > >>> for > >>>>>> new. > >>>>>> There are nouveau (masculine),
Re: [ofbiz-framework] branch trunk updated: Improved: no functional change, labels improvements
Good to see that the two of you confirm that cleanup can be combined with other improvements . Op do 3 feb. 2022 07:15 schreef Jacques Le Roux < jacques.le.r...@les7arts.com>: > Yep, thanks Michael, > > Jacques > > Le 02/02/2022 à 23:33, Michael Brohl a écrit : > > If I see it right, he has corrected wrong indentations. Nothing wrong > with that... > > > > Michael > > > > > > Am 02.02.22 um 18:00 schrieb Pierre Smits: > >> Hi Jacques, > >> > >> With this commit 8a9596be849f6709cb17c24a598c4862e8df867c you deleted > and > >> reinserted a lot of german translations (without any changes in the > >> translation at first glance). > >> > >> Were these necessary, or an unfortunate combination of circumstances > >> leading to you not working with a clean dev branch? It is a pity this > >> happened. Luckily, the impact is trivial. But people tend to get > confused > >> by this, and it could lead to complaints or heated arguments. > >> > >> Can you be a bit more careful next time around? > >> > >> Atentamente > >> 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 Sun, Jan 16, 2022 at 8:52 AM wrote: > >> > >>> This is an automated email from the ASF dual-hosted git repository. > >>> > >>> jleroux pushed a commit to branch trunk > >>> in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git > >>> > >>> > >>> The following commit(s) were added to refs/heads/trunk by this push: > >>> new 8a9596b Improved: no functional change, labels improvements > >>> 8a9596b is described below > >>> > >>> commit 8a9596be849f6709cb17c24a598c4862e8df867c > >>> Author: Jacques Le Roux > >>> AuthorDate: Sun Jan 16 08:51:03 2022 +0100 > >>> > >>> Improved: no functional change, labels improvements > >>> > >>> In French, and maybe other languages, there is not only one word > for > >>> new. > >>> There are nouveau (masculine), nouvelle (féminine) and nouvel > >>> (masculine followed > >>> by a word starting with a vowel) > >>> > >>> Here are few related changes with existing AccountingUiLabels, > >>> HumanResUiLabel > >>> changes and a new CommonUiLabels French labels improvements and > use of > >>> HumanResNew* labels in MainActionMenu of HumanresMenus.xml > >>> > >>> Also alongside replaces tabs by spaces in HumanResUiLabel > >>> --- > >>> .../accounting/config/AccountingUiLabels.xml | 2 +- > >>> applications/humanres/config/HumanResUiLabels.xml | 104 > >>> ++--- > >>> applications/humanres/widget/HumanresMenus.xml | 10 +- > >>> framework/common/config/CommonUiLabels.xml | 1 + > >>> 4 files changed, 59 insertions(+), 58 deletions(-) > >>> > >>> diff --git a/applications/accounting/config/AccountingUiLabels.xml > >>> b/applications/accounting/config/AccountingUiLabels.xml > >>> index 7c34628..b87f294 100644 > >>> --- a/applications/accounting/config/AccountingUiLabels.xml > >>> +++ b/applications/accounting/config/AccountingUiLabels.xml > >>> @@ -22296,7 +22296,7 @@ > >>> Hauptbuch Transaktion > >>> a Gl Transaction > >>> uno Transaccione GL > >>> -une opération comptable > >>> +une transaction comptable > >>> GLトランザクション > >>> Transaçõe contábei > >>> > >>> diff --git a/applications/humanres/config/HumanResUiLabels.xml > >>> b/applications/humanres/config/HumanResUiLabels.xml > >>> index 92d73e9..b77036a 100644 > >>> --- a/applications/humanres/config/HumanResUiLabels.xml > >>> +++ b/applications/humanres/config/HumanResUiLabels.xml > >>> @@ -856,7 +856,7 @@ > >>> 技能等級 > >>> > >>> > >>> -
Re: [ofbiz-framework] branch trunk updated: Improved: no functional change, labels improvements
Hi Jacques, With this commit 8a9596be849f6709cb17c24a598c4862e8df867c you deleted and reinserted a lot of german translations (without any changes in the translation at first glance). Were these necessary, or an unfortunate combination of circumstances leading to you not working with a clean dev branch? It is a pity this happened. Luckily, the impact is trivial. But people tend to get confused by this, and it could lead to complaints or heated arguments. Can you be a bit more careful next time around? Atentamente 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 Sun, Jan 16, 2022 at 8:52 AM wrote: > This is an automated email from the ASF dual-hosted git repository. > > jleroux pushed a commit to branch trunk > in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git > > > The following commit(s) were added to refs/heads/trunk by this push: > new 8a9596b Improved: no functional change, labels improvements > 8a9596b is described below > > commit 8a9596be849f6709cb17c24a598c4862e8df867c > Author: Jacques Le Roux > AuthorDate: Sun Jan 16 08:51:03 2022 +0100 > > Improved: no functional change, labels improvements > > In French, and maybe other languages, there is not only one word for > new. > There are nouveau (masculine), nouvelle (féminine) and nouvel > (masculine followed > by a word starting with a vowel) > > Here are few related changes with existing AccountingUiLabels, > HumanResUiLabel > changes and a new CommonUiLabels French labels improvements and use of > HumanResNew* labels in MainActionMenu of HumanresMenus.xml > > Also alongside replaces tabs by spaces in HumanResUiLabel > --- > .../accounting/config/AccountingUiLabels.xml | 2 +- > applications/humanres/config/HumanResUiLabels.xml | 104 > ++--- > applications/humanres/widget/HumanresMenus.xml | 10 +- > framework/common/config/CommonUiLabels.xml | 1 + > 4 files changed, 59 insertions(+), 58 deletions(-) > > diff --git a/applications/accounting/config/AccountingUiLabels.xml > b/applications/accounting/config/AccountingUiLabels.xml > index 7c34628..b87f294 100644 > --- a/applications/accounting/config/AccountingUiLabels.xml > +++ b/applications/accounting/config/AccountingUiLabels.xml > @@ -22296,7 +22296,7 @@ > Hauptbuch Transaktion > a Gl Transaction > uno Transaccione GL > -une opération comptable > +une transaction comptable > GLトランザクション > Transaçõe contábei > > diff --git a/applications/humanres/config/HumanResUiLabels.xml > b/applications/humanres/config/HumanResUiLabels.xml > index 92d73e9..b77036a 100644 > --- a/applications/humanres/config/HumanResUiLabels.xml > +++ b/applications/humanres/config/HumanResUiLabels.xml > @@ -856,7 +856,7 @@ > 技能等級 > > > - Fähigkeit Typ ID > +Fähigkeit Typ ID > Skill Type ID > Id tipo de habilidad > Compétence > @@ -882,7 +882,7 @@ > 技能掌握日期 > > > - temporäres Kennzeichen > +temporäres Kennzeichen > Temporary Flag > Indicador Principal > Balise temporaire > @@ -895,7 +895,7 @@ > 是否為臨時 > > > - Nummer des Kündigungsgrundes > +Nummer des Kündigungsgrundes > Termination Reason ID > Id de razón de finiquito > Motif de la fin de contrat > @@ -908,7 +908,7 @@ > 雇佣終止原因識別 > > > - Kündigungsart ID > +Kündigungsart ID > Termination Type ID > Id tipo de finiquito > Type de fin de contrat > @@ -921,7 +921,7 @@ > 雇佣終止類型識別 > > > - Titel > +Titel > Title > Título > Titre > @@ -931,7 +931,7 @@ > 標題 > > > - Nummer der Schulungsklasse > +Nummer der Schulungsklasse > Training Class Type ID > ID de tipo de clase de capacitación > Type de formation > @@ -943,7 +943,7 @@ > 教育訓練課程類型識別 > > > - Anfragenummer der Schulung > +Anfragenummer der Schulung > Training Request ID > ID de solicitud de capacitación > Approbation > @@ -953,7 +953,7 @@ > 教育訓練請求標識 > > > - Datum des Arbeitslos
[jira] [Updated] (OFBIZ-12554) Quote Edit - wrong decorator screen used
[ https://issues.apache.org/jira/browse/OFBIZ-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12554: - Description: Currently, the EditQuote screen in QuoteScreens.xml is using 'main-decorator' as the decorator-screen reference screen. To demo/test: https://localhost:8443/ordermgr/control/EditQuote?quoteId=CQ0001 Because of this, the menus for the quote (being edited) are not shown to the user. was: Currently, the EditQuote screen in QuoteScreens.xml is using 'main-decorator' as the decorator-screen reference screen. Because of this, the menus for the quote (being edited) are not shown to the user. > Quote Edit - wrong decorator screen used > - > > Key: OFBIZ-12554 > URL: https://issues.apache.org/jira/browse/OFBIZ-12554 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Upcoming Branch >Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Labels: consistency, decorator, usability, user-experience > > Currently, the EditQuote screen in QuoteScreens.xml is using 'main-decorator' > as the decorator-screen reference screen. > To demo/test: https://localhost:8443/ordermgr/control/EditQuote?quoteId=CQ0001 > Because of this, the menus for the quote (being edited) are not shown to the > user. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: [jira] [Updated] (OFBIZ-6349) Replace ViewQuoteItems.ftl with form widgets
Hi Nicolas, Christian, Are you both still collaborating to get this issue successfully resolved? It seems to me that the both of you, being privileged contributors, should easily get this in play. 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, Sep 18, 2015 at 4:20 PM Michael Brohl (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/OFBIZ-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Michael Brohl updated OFBIZ-6349: > - > Sprint: Community Day 2 - 2015, Community Day 3 - 2015 (was: > Community Day 2 - 2015) > > > Replace ViewQuoteItems.ftl with form widgets > > > > > > Key: OFBIZ-6349 > > URL: https://issues.apache.org/jira/browse/OFBIZ-6349 > > Project: OFBiz > > Issue Type: Improvement > > Components: order > >Affects Versions: Trunk > >Reporter: Christian Carlow > >Assignee: Nicolas Malin > > Attachments: OFBIZ-6349.patch > > > > > > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
[jira] [Created] (OFBIZ-12554) Quote Edit - wrong decorator screen used
Pierre Smits created OFBIZ-12554: Summary: Quote Edit - wrong decorator screen used Key: OFBIZ-12554 URL: https://issues.apache.org/jira/browse/OFBIZ-12554 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, the EditQuote screen in QuoteScreens.xml is using 'main-decorator' as the decorator-screen reference screen. Because of this, the menus for the quote (being edited) are not shown to the user. -- This message was sent by Atlassian Jira (v8.20.1#820001)
