January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2205) Issues in KIE WB

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2205?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2205: ------------------------------------- Assignee: Toni Rikkola (was: Edson Tirelli) > Issues in KIE WB > ---------------- > > Key: DROOLS-2205 > URL: https://issues.jboss.org/browse/DROOLS-2205 > Project: Drools > Issue Type: Bug > Affects Versions: 7.4.1.Final > Reporter: Senthil Kumar Kamaraj > Assignee: Toni Rikkola > > There are some issues in KIE workbench 7.4.1 release > 1. Creating group on KIE WB on tomcat throws exception sometimes, but the group is created. > 2. When trying to delete the user from KIE WB, the user is not getting deleted. > 3. Language support other than English is not complete: partial support > 4. Sometimes, when I am trying to perform operation on "newly created project" in KIE Workbench, URL is redirected to other existing project. > 5. KIE WB user creation: Unable to create new user gracefully from the GUI: error: Cannot read property 'p8b' of null. > > 6. The new user creation is failing if it is assigned to Groups and Roles. > Received Error : Group not found. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3491) Allow to add a key-store and generate a key-pair inside the same composite

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3491: -------------------------------------------- Summary: Allow to add a key-store and generate a key-pair inside the same composite Key: WFCORE-3491 URL: https://issues.jboss.org/browse/WFCORE-3491 Project: WildFly Core Issue Type: Enhancement Components: Security Reporter: Jean-Francois Denise Assignee: Darran Lofthouse I am facing an issue with key-store 'add' and 'generate-key-pair' operations being located in the same composite: "WFLYELY00007: The required service 'service org.wildfly.security.key-store.generated_ks' is not UP, it is currently 'STARTING'." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9574) Distribution files does not have POSIX permissions perfectly set

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9574?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on WFLY-9574: -------------------------------------- It turns out that the Wildfly builds are associating the files with the proper permissions. The issue is only on the EAP builds. Thus, I'm closing this issue. > Distribution files does not have POSIX permissions perfectly set > ---------------------------------------------------------------- > > Key: WFLY-9574 > URL: https://issues.jboss.org/browse/WFLY-9574 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Affects Versions: 11.0.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. > While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). Specifically, .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; > On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. > I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2181) Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2181?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2181: ---------------------------------------- The problem was caused by https://issues.jboss.org/browse/GUVNOR-3524 > Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks > ----------------------------------------------------------------- > > Key: DROOLS-2181 > URL: https://issues.jboss.org/browse/DROOLS-2181 > Project: Drools > Issue Type: Bug > Components: Guided Decision Tree Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > - Double-click on a node (object/action) to edit/delete/collapse. > - Pop-up shows the icons/buttons. > - Click on Edit/Delete/collapse icon. Icons are frozen. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1369) FIPS mode, Elytron HTTP DIGEST authentication mechanism not fips compliant

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1369?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1369: ----------------------------------- So do I understand correctly, that to enable new mechanisms only thing to do is to specify auth-method in web.xml to be DIGEST-SHA-256 or DIGEST-SHA-512-256 ? > FIPS mode, Elytron HTTP DIGEST authentication mechanism not fips compliant > -------------------------------------------------------------------------- > > Key: ELY-1369 > URL: https://issues.jboss.org/browse/ELY-1369 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.2.0.Beta3 > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.2.0.Beta11 > > > Elytron HTTP DIGEST authentication comply to rfc2617 - which means MD5 is used by default (it means it is hardcode, with no way to configure another hash algorithm). But MD5 could make troubles in fips environment [5]. > {code:java|title=DigestAuthenticationMechanism.java} > String algorithm = convertToken(ALGORITHM, responseTokens.get(ALGORITHM)); > if (MD5.equals(algorithm) == false) { > throw log.mechUnsupportedAlgorithm(getMechanismName(), algorithm); > } > {code} > There exists proposed rfc7616 which makes algorithm configurable, work on new DIGEST features are covered by [1]. [~dlofthouse] is it planned for [1] to target 7.1? > [1] https://issues.jboss.org/browse/ELY-286 > [2] https://developer.jboss.org/wiki/ElytronHTTPDigestNonceHandling-Design > [3] https://tools.ietf.org/html/rfc2617 > [4] https://tools.ietf.org/html/rfc7616 > [5] https://access.redhat.com/support/cases/#/case/01761455 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2212) [DMN Editor] Relation and Invocation can not be saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2212?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2212: -------------------------------- QE Status: ON_QA (was: NEW) > [DMN Editor] Relation and Invocation can not be saved > ----------------------------------------------------- > > Key: DROOLS-2212 > URL: https://issues.jboss.org/browse/DROOLS-2212 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: error.log > > > Save operation in dmn editor throws an exception if the dmn diagram contains decision node holding relation or invocation context entry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2212) [DMN Editor] Relation and Invocation can not be saved

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2212: ----------------------------------- Summary: [DMN Editor] Relation and Invocation can not be saved Key: DROOLS-2212 URL: https://issues.jboss.org/browse/DROOLS-2212 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: error.log Save operation in dmn editor throws an exception if the dmn diagram contains decision node holding relation or invocation context entry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-283 at 1/4/18 7:46 AM: -------------------------------------------------------- For needs of OpenJDK patch review I has prepared simple reproducer without AS: [^reproducer-gss.zip] {panel} Hi, I was just able to prepare usable reproducer (attaching in ZIP file) and fixing patch of JDK (attaching too). Before I was able to make my usecase working, I has found second issue too - I has included it too. Issues and their reproducing: *1) already described problem of wrong initialized SunNativeProvider.INSTANCE* This can be reproduced by recreating GSSManager before createGSSContext - ProviderList.factories will be initialized as part of initSecContext/acceptSecContext which will cause using wrong initialized SunNativeProvider.INSTANCE and described exception. *2) when channel binding is used SIGSEGV occure* This can be reproduced by setting channel binding without initAddr/acceptAddr. This is caused by sending uninitialized (with random length) cb->initiator_address from JDK to the kerberos. (It is used by krb library for messages checksum calculation even when addrtype is GSS_C_AF_NULLADDR.) Attached reproducer-gss.zip reproduces both issues and attached patch fixes both. I would welcome merging into OpenJDK. (I am covered by OCA of Red Hat) This issue affect both tested JDKs, JKD8u121 and upstream JDK9 from mercurial master. Thanks, Jan {panel} Also reported as Oracle JDK issues: * 1) as [JDK-8194073|https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8194073] * 2) as [JDK-8194630|https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8194630] was (Author: honza889): For needs of OpenJDK patch review I has prepared simple reproducer without AS: [^reproducer-gss.zip] {panel} Hi, I was just able to prepare usable reproducer (attaching in ZIP file) and fixing patch of JDK (attaching too). Before I was able to make my usecase working, I has found second issue too - I has included it too. Issues and their reproducing: *1) already described problem of wrong initialized SunNativeProvider.INSTANCE* This can be reproduced by recreating GSSManager before createGSSContext - ProviderList.factories will be initialized as part of initSecContext/acceptSecContext which will cause using wrong initialized SunNativeProvider.INSTANCE and described exception. *2) when channel binding is used SIGSEGV occure* This can be reproduced by setting channel binding without initAddr/acceptAddr. This is caused by sending uninitialized (with random length) cb->initiator_address from JDK to the kerberos. (It is used by krb library for messages checksum calculation even when addrtype is GSS_C_AF_NULLADDR.) Attached reproducer-gss.zip reproduces both issues and attached patch fixes both. I would welcome merging into OpenJDK. (I am covered by OCA of Red Hat) This issue affect both tested JDKs, JKD8u121 and upstream JDK9 from mercurial master. Thanks, Jan {panel} > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: jkalina-openjdk-native-gss.patch, openjdk-patch-native-mechs.patch, reproducer-gss.zip > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina resolved ELY-283. ---------------------------- Resolution: Done > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: jkalina-openjdk-native-gss.patch, openjdk-patch-native-mechs.patch, reproducer-gss.zip > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-283 at 1/4/18 7:43 AM: -------------------------------------------------------- Complete instructions to setup wildfly+elytron to use gssapi composed into tutorial: https://hkalina.github.io/2018/01/02/gssproxy/ Things to fix/improve in elytron: * path to the keytab in kerberos-security-factory should be made optional * workaround JDK-8194073 - wil not fix GS2-KRB5, but will fix GSSAPI (!) -> ELY-85 was (Author: honza889): Complete instructions to setup wildfly+elytron to use gssapi composed into tutorial: https://hkalina.github.io/2018/01/02/gssproxy/ Things to fix/improve in elytron: * path to the keytab in kerberos-security-factory should be made optional * workaround JDK-8194073 - wil not fix GS2-KRB5, but will fix GSSAPI (!) > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: jkalina-openjdk-native-gss.patch, openjdk-patch-native-mechs.patch, reproducer-gss.zip > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018