May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4960) org.jboss.as.cli warning without message when running boot hook script

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4960?page=com.atlassian.jira.plug... ] Jean Francois Denise moved JBEAP-19422 to WFCORE-4960: ------------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4960 (was: JBEAP-19422) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: OpenShift) > org.jboss.as.cli warning without message when running boot hook script > ---------------------------------------------------------------------- > > Key: WFCORE-4960 > URL: https://issues.redhat.com/browse/WFCORE-4960 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > Warnings occurs during ha-load scenarios > {noformat} > 33m15:12:11,879 WARN [org.jboss.as.cli] (Controller Boot Thread) > {noformat} > See [logs in jenkins jobs|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-o...] > *Steps to reproduce:* > * Use CD19 settings on openshift-eap-tests (see for example [this branch|https://gitlab.mw.lab.eng.bos.redhat.com/mkopecky/openshift-eap-te...]) > * mvn clean test -B -Pcd -Dtest=HAEjbCounterTest -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5301) DMN Strongly assess DMN Import with same name in 2 namespaces

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5301?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5301: ----------------------------------- Description: check same ItemDefinition name, defined in 2 models, where one imports the other > DMN Strongly assess DMN Import with same name in 2 namespaces > ------------------------------------------------------------- > > Key: DROOLS-5301 > URL: https://issues.redhat.com/browse/DROOLS-5301 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > check same ItemDefinition name, defined in 2 models, where one imports the other -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5302) DMN Strongly assess collection of collection deep nesting

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5302: -------------------------------------- Summary: DMN Strongly assess collection of collection deep nesting Key: DROOLS-5302 URL: https://issues.redhat.com/browse/DROOLS-5302 Project: Drools Issue Type: Task Components: core engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5301) DMN Strongly assess DMN Import with same name in 2 namespaces

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5301: -------------------------------------- Summary: DMN Strongly assess DMN Import with same name in 2 namespaces Key: DROOLS-5301 URL: https://issues.redhat.com/browse/DROOLS-5301 Project: Drools Issue Type: Task Components: core engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5300) DMN Strongly assess Anonymous inner composite collection

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5300: -------------------------------------- Summary: DMN Strongly assess Anonymous inner composite collection Key: DROOLS-5300 URL: https://issues.redhat.com/browse/DROOLS-5300 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on WFCORE-4959: ------------------------------------------ This would be quite a big change, the module --add command within the CLI just operates on the local filesystem and writes the module directly, once you start talking about domain mode this converts this to more of a management level operation to distribute an operation across the host controllers. Once talking about the host controllers you can identify the currently running host controllers but if you wanted to target the ones not presently running / the ones to run in the the future tracking those becomes more complex. I have also in the past wondered if we could so something where if a slave does not have a module requested it tries to pull it from the master which would save the coordination of a command like this but potentially brings in new problems such as mixed domains where different versions of modules are required or modules with optional dependencies where the missing module is intended. > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Joao Paulo Goncalves > Assignee: Brian Stansberry > Priority: Major > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Darran Lofthouse moved WFLY-13430 to WFCORE-4959: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4959 (was: WFLY-13430) > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Joao Paulo Goncalves > Assignee: Brian Stansberry > Priority: Major > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1139) Automate Gateway fix https://github.com/kiali/kiali-ui/pull/1771

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1139?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1139. ----------------------------------- Resolution: Done > Automate Gateway fix https://github.com/kiali/kiali-ui/pull/1771 > ---------------------------------------------------------------- > > Key: SWSQE-1139 > URL: https://issues.redhat.com/browse/SWSQE-1139 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1139) Automate Gateway fix https://github.com/kiali/kiali-ui/pull/1771

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1139?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1139: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/286 https://github.com/Kiali-QE/kiali-qe-python/pull/287 > Automate Gateway fix https://github.com/kiali/kiali-ui/pull/1771 > ---------------------------------------------------------------- > > Key: SWSQE-1139 > URL: https://issues.redhat.com/browse/SWSQE-1139 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13319) Wildfly 19 MP-JWT & EJB Integration

by Radu Cimpean (Jira)

[ https://issues.redhat.com/browse/WFLY-13319?page=com.atlassian.jira.plugi... ] Radu Cimpean commented on WFLY-13319: ------------------------------------- Cheers, [~dlofthouse]. Thanks for both the stack and for looking into it. Looking forward to the support being added. All the best, stay safe. > Wildfly 19 MP-JWT & EJB Integration > ----------------------------------- > > Key: WFLY-13319 > URL: https://issues.redhat.com/browse/WFLY-13319 > Project: WildFly > Issue Type: Feature Request > Components: EJB, MP JWT, Test Suite > Affects Versions: 19.0.0.Final > Reporter: Radu Cimpean > Assignee: Darran Lofthouse > Priority: Major > Fix For: 20.0.0.Beta1 > > Attachments: server-cli.txt, web.xml > > > ===Previous configuration & situation=== > As written https://groups.google.com/forum/#!topic/wildfly/L1BxATschCU, > We were running wildfly 18 and used jwt for securing the application. We did this via a series of cli commands (see server-cli.txt) to configure the server, as well as referencing the created domains in the web.xml. > Under jboss-web.xml we are referencing the "ejb-domain" created in the CLIs. The web.xml (see attachments) protects the resource wit the role referenced in the CLIs (role present in the token) > All our jax-rs resources are annotated with @Stateless and are calling EJBs which in turn are @Statless and declare allowed roles. > ===Current situation=== > We've upgraded to wildfly 19 in hopes of using microprofile jwt. To do this, we've annotated the Application class with > @LoginConfig(authMethod = "MP-JWT", realmName = "MP-JWT-REALM"), removed the login-config from the web.xml, and removed the security-domain from jboss-web.xml (since otherwise I would receive an error: ELY01148: A SecurityDomain has already been associated with the specified ClassLoader"). > After also removing the security-constraint tag from the web.xml I was able to get to the resource and noticed that the JWTToken was properly injected (all claims and entries are there), and the SecurityContext injected in the resource also contained the jwt specific values. From what I can tell, in the context of the jax-rs classloader, I am authenticated. > I would, however, always receive a "Invocation on method... is not allowed" the second the resource would try calling a bean, even if the role matched. Upon checking the logs, and what the injected SessionContext contained, I noticed the principal was anonymous and had no roles allowed. > I therefore believe that the credentials are somehow not being properly passed. > Is there a documented way of properly integrating jax-rs&ejb with microprofile jwt? -- 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 May 2020