September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4527) [DMN Designer] Search feature - Check session for all events that affects search components

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4527: --------------------------------------- Summary: [DMN Designer] Search feature - Check session for all events that affects search components Key: DROOLS-4527 URL: https://issues.jboss.org/browse/DROOLS-4527 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Check session for all events that trigger some action into search components. Here's an occurrence: DMNDiagramEditor.java onRefreshFormPropertiesEvent. The JIRA comprehends the fix for this and any other similar occurrence. --- This JIRA was created to address this issue: https://github.com/kiegroup/kie-wb-common/pull/2853#discussion_r322098627 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12549) mp.metrics.tags does not work when specified in MP config subsystem

by Richard DiCroce (Jira)

Richard DiCroce created WFLY-12549: -------------------------------------- Summary: mp.metrics.tags does not work when specified in MP config subsystem Key: WFLY-12549 URL: https://issues.jboss.org/browse/WFLY-12549 Project: WildFly Issue Type: Bug Components: MP Metrics Affects Versions: 18.0.0.Beta1 Reporter: Richard DiCroce Assignee: Jeff Mesnil Section 3.1.2 of the MP Metrics spec states: {quote} Tags can be supplied in two ways: ... At the application server level by using MicroProfile Config and setting a configuration property of the name mp.metrics.tags. {quote} This does not work in WildFly if the property is configured inline in the Microprofile Config subsystem like this: {code} <subsystem xmlns="urn:wildfly:microprofile-config-smallrye:1.0"> <config-source name="props"> <property name="mp.metrics.tags" value="foo=bar"/> </config-source> </subsystem> {code} Workaround: specify it under <system-properties> instead. This works as expected: {code} <system-properties> <property name="mp.metrics.tags" value="foo=bar"/> </system-properties> {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12548) Upgrade WildFly Core 10.0.0.Beta8

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12548?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-12548: ------------------------------- Summary: Upgrade WildFly Core 10.0.0.Beta8 (was: Upgrade WildFly Core 10.0.0.Beta7) > Upgrade WildFly Core 10.0.0.Beta8 > --------------------------------- > > Key: WFLY-12548 > URL: https://issues.jboss.org/browse/WFLY-12548 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12433) Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final

by Ronald Sigal (Jira)

[ https://issues.jboss.org/browse/WFLY-12433?page=com.atlassian.jira.plugin... ] Ronald Sigal resolved WFLY-12433. --------------------------------- Release Notes Text: https://github.com/tomjenkinson/jboss-as/pull/8 merged into https://github.com/tomjenkinson/jboss-as Resolution: Done > Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final > ----------------------------------------------- > > Key: WFLY-12433 > URL: https://issues.jboss.org/browse/WFLY-12433 > Project: WildFly > Issue Type: Sub-task > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 18.0.0.Beta1 > > > JBoss Jakarta JAX-RS API fork: > https://github.com/jboss/jboss-jakarta-jaxrs-api_spec/ -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2381) LOCAL_PING should update PingData.isCoord on view changes

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2381?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2381: --------------------------- Fix Version/s: 4.1.5 > LOCAL_PING should update PingData.isCoord on view changes > --------------------------------------------------------- > > Key: JGRP-2381 > URL: https://issues.jboss.org/browse/JGRP-2381 > Project: JGroups > Issue Type: Bug > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.5 > > > LOCAL_PING creates a {{PingData}} instance for the local node when it receives the {{CONNECT}} event and sets {{isCoord()}} based on the {{PingData}} instances added by other nodes. It should set {{isCoord()}} on {{VIEW_CHANGE}} instead, so that after a merge new nodes send the join request to the merge coordinator and not to the first node that started. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3747) Enhance credential-store description related to location and type attributes

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3747?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3747: -------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.Beta7) > Enhance credential-store description related to location and type attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-3747 > URL: https://issues.jboss.org/browse/WFCORE-3747 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Claudio Miranda > Assignee: Darran Lofthouse > Priority: Major > Fix For: 10.0.0.Final > > > The description for "location" and "type" for credential-store resource is displayed below. > Following discussion of WFCORE-3458, the "location" attribute is required only when the "type" is file based, but the description doesn't says that, the description may be improved to reflect this behavior and list the possible file based types. > When the user doesn't set the "type" attribute it defaults to "JCEKS", but there is no "default" value on resource description for "type" attribute. > {code} > "location" => { > "type" => STRING, > "description" => "File name of credential store storage.", > "attribute-group" => "implementation", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > "type" => { > "type" => STRING, > "description" => "The credential store type, e.g. KeyStoreCredentialStore.", > "attribute-group" => "implementation", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-2496: -------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.Beta7) > Functionality in WildFly to encrypt database passwords > ------------------------------------------------------ > > Key: WFCORE-2496 > URL: https://issues.jboss.org/browse/WFCORE-2496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Carlton Zachary > Assignee: Farah Juma > Priority: Major > Fix For: 10.0.0.Final > > > Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml. > Thanks -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFCORE-944: ------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.Beta7) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.jboss.org/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > Fix For: 10.0.0.Final > > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4540) Add error message with information that is not allowed to read secret-value and entry-type from Credential Store

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4540?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4540: -------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.Beta7) > Add error message with information that is not allowed to read secret-value and entry-type from Credential Store > ---------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4540 > URL: https://issues.jboss.org/browse/WFCORE-4540 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 10.0.0.Final > > > Add error message with information that is not allowed to read secret-value and entry-type from Credential Store over CLI. > This CLI commands > {code} > /subsystem=elytron/credential-store=testCS/alias=someAlias:read-attribute(name=secret-value) > /subsystem=elytron/credential-store=testCS/alias=someAlias:read-attribute(name=entry-type) > {code} > end with success result. > {code} > { > "outcome" => "success", > "result" => undefined > } > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4407) Cannot configure Elytron security domain using embedded server in admin mode

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4407?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4407: -------------------------------- Fix Version/s: 10.0.0.Final (was: 10.0.0.Beta7) > Cannot configure Elytron security domain using embedded server in admin mode > ---------------------------------------------------------------------------- > > Key: WFCORE-4407 > URL: https://issues.jboss.org/browse/WFCORE-4407 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Environment: > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Fix For: 10.0.0.Final > > > There are some configurations that are impossible to do using the embedded server, for example, we cannot create a security domain in Elytron that references a security domain in the security subsystem: > {noformat} > embed-server --server-config=standalone-full-ha.xml --std-out=echo > /subsystem=security/security-domain=my-sec-domain:add(cache-type=default) > /subsystem=security/security-domain=my-sec-domain/authentication=classic:add(login-modules=[{code=RealmUsersRoles, flag=required, module=RealmUsersRoles, module-options=[("usersProperties"=>"usersProperties"),("rolesProperties"=>"rolesProperties")]}]) > /subsystem=security/elytron-realm=my-sec-domain:add(legacy-jaas-config=my-sec-domain) > /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) > stop-embedded-server > {noformat} > The execution of these operations in an embedded server running in admin-mode throws the following error: > {noformat} > [standalone@embedded /] /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) > 12:30:53,429 ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "my-sec-domain") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] > } > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] > }, > "rolled-back" => true > } > {noformat} > The problem here is Elytron security domain services cannot be up because they require the legacy installed realm services, which are not up when we are using embedded in admin-only mode. > The SecurityDomain advertises no runtime operation, if no services are installed that would ever depend on security domain we may be able to skip installing some of these services entirely and allow their configuration in embedded / admin-only. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019