July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5042) Upgrade WildFly Elytron to 1.13.0.CR2

by Farah Juma (Jira)

Farah Juma created WFCORE-5042: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.13.0.CR2 Key: WFCORE-5042 URL: https://issues.redhat.com/browse/WFCORE-5042 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELY-2010) Release WildFly Elytron 1.13.0.CR2

by Farah Juma (Jira)

Farah Juma created ELY-2010: ------------------------------- Summary: Release WildFly Elytron 1.13.0.CR2 Key: ELY-2010 URL: https://issues.redhat.com/browse/ELY-2010 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.13.0.CR2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELY-1879) Support SSH authentication for Git persistence

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1879?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1879: ---------------------------- Fix Version/s: 1.13.0.CR2 > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: ELY-1879 > URL: https://issues.redhat.com/browse/ELY-1879 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > Fix For: 1.13.0.CR2 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELY-1951) Add version 1.6 of the Elytron client schema

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1951?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1951: ---------------------------- Fix Version/s: 1.13.0.CR2 > Add version 1.6 of the Elytron client schema > -------------------------------------------- > > Key: ELY-1951 > URL: https://issues.redhat.com/browse/ELY-1951 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: 1.13.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5044) Allow to set default value for columns other than 'literal equals to ...'

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5044?page=com.atlassian.jira.plug... ] Jozef Marko resolved DROOLS-5044. --------------------------------- Fix Version/s: 7.41.0.Final Resolution: Done Marking as resolved, as the related jira is done > Allow to set default value for columns other than 'literal equals to ...' > ------------------------------------------------------------------------- > > Key: DROOLS-5044 > URL: https://issues.redhat.com/browse/DROOLS-5044 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Werner Van Herrewegen > Assignee: Michael Anstis > Priority: Major > Fix For: 7.41.0.Final > > Attachments: image-2020-02-11-14-10-05-686.png, image-2020-02-11-14-28-02-448.png > > > Hi, > Sometimes I need to be able to put a +default 'TRUE'+ value for conditional columns that don't make any sense to have a 'FALSE' value. > I give you the following case: > When I want to update a fact A in the action part based on the value of a fact B on the condition part, it obviously makes sense to have an additional condition that fact A exists. > But this results (as seen in the example screenshot below) in the option to flag the column that fact A exists TRUE/FALSE with a 'default' on FALSE. > When you leave it FALSE, you get a compile error because the resulting rule code excludes the line, when you flag it TRUE, the line is shown ok and you don't get any errors. > So the only real value that is possible is TRUE and it must be flagged TRUE for each row in the decision table. > It is really hard for me to explain this to business users, when I give them the option to uncheck the column. > Workaround/solution would be to allow a default value 'TRUE' and actually hide the column. > Because for the business person, he doesn't care. > And the pity is that there actually is an option to add default values but only for literal equals... > More generally this is a need to add some rule text that is always in the generated resulting rule code in the LHS or RHS rule part for all rows in the decision table. > kr, > Werner -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13658) Active session statistics incorrectly reported for non-tx invalidation caches

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13658?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-13658: --------------------------------- Labels: downstream_dependency (was: ) > Active session statistics incorrectly reported for non-tx invalidation caches > ----------------------------------------------------------------------------- > > Key: WFLY-13658 > URL: https://issues.redhat.com/browse/WFLY-13658 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Minor > Labels: downstream_dependency > > The active session count returns the number of sessions in memory that are owned by the current member. For non-transactional invalidation caches, sessions are always owned by the same member, thus all members except one will always return an active session count of 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13660) The legacy security subsystem should register a capability if it is initialising JACC

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13660: --------------------------------------- Summary: The legacy security subsystem should register a capability if it is initialising JACC Key: WFLY-13660 URL: https://issues.redhat.com/browse/WFLY-13660 Project: WildFly Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 Decisions regarding if JACC processing for deployment should take place should be driven based on if a subsystem is initialising JACC - not on if one of the subsystems is present as they could be configured so that neither enable JACC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-13641: -------------------------------------- There are cases where this is already used apparently. In the PR we just found a bug where this breaks opentracing integration which requires CDI to scan the archive and find beans. I think not being able to index it was somehow linked to the deployment structure descriptor - e,g, it was intentional that we couldn't see Jandex, but our processor was incorrectly trying to index it nonetheless. But I am not 100% sure. > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13641 > URL: https://issues.redhat.com/browse/WFLY-13641 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 20.0.0.Final > Reporter: Jens Viebig > Assignee: Matěj Novotný > Priority: Major > > When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class: > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > Seems VFS cannot get hold of the classes. > The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13587) Smallrye OpenAPI throws java.lang.NullPointerException because of null parameter schema

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFLY-13587?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Smietanko updated WFLY-13587: -------------------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Smallrye OpenAPI throws java.lang.NullPointerException because of null parameter schema > --------------------------------------------------------------------------------------- > > Key: WFLY-13587 > URL: https://issues.redhat.com/browse/WFLY-13587 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > This was spotted while running RESTEasy test suite against EAP XP 1.0.0 CR1 and CR2. > Initially it seemed that the specific test case [1] was failing due to the same root cause of those tracked by the following issue: > * https://issues.redhat.com/browse/JBEAP-19600 > > Eventually it turned out that the changes to fix the above mentioned issue didn't solve this specific test case failures and a deeper investigation was done, see [2]. > Specifically a strange behavior is represented by the fact that the reproducer built manually by using the same resources used by the test case could be deployed successfully while the WAR archive generated by Arquillian in the RESTEasy TS was failing to deploy regularly. > The investigation detailed at https://github.com/smallrye/smallrye-open-api/issues/353#issuecomment-639... provided evidence that there are some cases in which the parameter schema would be set to null, so the issue [2] was created upstream. > [1] > https://github.com/resteasy/Resteasy/blob/3.11/testsuite/integration-test... > [2] > https://github.com/smallrye/smallrye-open-api/issues/359 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13659) Fix modules with dependency on Legacy Security Subsystem or PicketBox

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13659: --------------------------------------- Summary: Fix modules with dependency on Legacy Security Subsystem or PicketBox Key: WFLY-13659 URL: https://issues.redhat.com/browse/WFLY-13659 Project: WildFly Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 Various subsystems have dependencies on the legacy security subsystem, these need to be verified to make sure they are really required or adjusted to make optional. *org.jboss.as.security* {code} ./system/layers/base/org/wildfly/extension/request-controller/main/module.xml: <module name="org.jboss.as.security" optional="true"/> ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.jboss.as.security" optional="true"/> ./system/layers/base/org/wildfly/extension/elytron/main/module.xml: <module name="org.jboss.as.security-integration" optional="true" services="import"/> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.jboss.as.security" optional="true"/> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <main-class name="org.jboss.as.security.vault.VaultTool"/> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.jboss.as.security" optional="true"/> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.jboss.as.security"/> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.jboss.as.security" optional="true" services="import"/> ./system/layers/base/org/jboss/as/weld/common/main/module.xml: <module name="org.jboss.as.security" optional="true"/> {code} *org.picketbox* {code} ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/wildfly/extension/batch/jberet/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/wildfly/iiop-openjdk/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/picketlink/federation/bindings/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/picketlink/federation/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/security-api/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/jboss/as/weld/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/domain-management/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/jboss/as/cli/main/module.xml: <module name="org.picketbox" optional="true"/> ./system/layers/base/org/jboss/as/security/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/as/security-integration/main/module.xml: <module name="org.picketbox"> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-client/main/module.xml: <module name="org.picketbox" export="true"/> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-server/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/ws/jaxws-client/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/ironjacamar/impl/main/module.xml: <module name="org.picketbox"/> ./system/layers/base/org/jboss/security/negotiation/main/module.xml: <module name="org.picketbox"/> {code} The optional dependencies are probably Ok but the non-optional dependencies mean these will pull in the modules we do not want when these subsystems are provisioned. As there are quite a few affected modules I will likely group these into related areas and create sub tasks to track the individual problems to be addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 July 2020