December 2017 - jboss-jira - Jboss List Archives

[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 reassigned ELY-283: ------------------------------ Assignee: Jan Kalina > 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 > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2157: ---------------------------------------- Things to do: * Add a new {{ContextEntry}} to the definition for the last row. * Use a default (variable) "name" for the {{ContextEntry}}. This may become irrelevant if the grid rendering changes to ignore the "name" column. * Prevent editing the "name" for the last {{ContextEntry}} * Prevent dragging the last row, or other rows past the last row. * Prevent deleting the last row (it is impossible to delete rows at the moment!) * Insert new {{ContextEntry}} rows before the last row. > DMN Editor: Contexts: Add special behaviour of last row > ------------------------------------------------------- > > Key: DROOLS-2157 > URL: https://issues.jboss.org/browse/DROOLS-2157 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row: > {code} > <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f"> > <semantic:contextEntry> > <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/> > <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4"> > <semantic:text>"literal exp" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > <semantic:contextEntry> > <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5"> > <semantic:text>"result" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > </semantic:context> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1359) Missing configuration elements in the XA DataSources

by Alexis Hassler (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1359?page=com.atlassian.jira.plugin... ] Alexis Hassler updated JBJCA-1359: ---------------------------------- Forum Reference: https://developer.jboss.org/message/978578 > Missing configuration elements in the XA DataSources > ---------------------------------------------------- > > Key: JBJCA-1359 > URL: https://issues.jboss.org/browse/JBJCA-1359 > Project: IronJacamar > Issue Type: Feature Request > Components: Embedded > Affects Versions: 1.4.5 > Reporter: Alexis Hassler > > When I start a XA DataSource with IJ Embedded, some configuration are not used, including <prepared-statement-cache-size> and <valid-connection-checker>. > These elements are correctly loaded for none-XA datasources but are ignored for XA datasources. > I've isolated the problem in a simple test case at https://gitlab.com/hasalex/sw-ijembed/. > The failing test can be seen in the CI : https://gitlab.com/hasalex/sw-ijembed/-/jobs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1392) Undeploy doesn't remove Data content if server is in --admin-only mode

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1392?page=com.atlassian.jira.plugi... ] Tomas Hofman commented on WFCORE-1392: -------------------------------------- As for full replace deployment, the handler already removes the content in both modes - no changes are required and it's also not affected by modifications in DeploymentRemoveHandler. {code} DeploymentFullReplaceHandler: remove old resource contentRepository.addContent(new content) or contentRepository.syncContent(new content) create new resource if (ENABLED): DeploymentHandlerUtil.replace(...) // basically just removes old services and creates new ones else: DeploymentHandlerUtil.undeploy(...) complete step: if (new and old content hashes differ, or new content is unmanaged): contentRepository.removeContent(...) if (is managed content): contentRepository.addContentReference(...) {code} The domain controller's DeploymentFullReplaceHandler works very similarly, also removing content in the complete step of the main step (so in both modes). > Undeploy doesn't remove Data content if server is in --admin-only mode > ----------------------------------------------------------------------- > > Key: WFCORE-1392 > URL: https://issues.jboss.org/browse/WFCORE-1392 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.1.0.CR2 > Reporter: Chao Wang > Assignee: Tomas Hofman > Priority: Minor > > {noformat} > Steps to Reproduce: > 1. Start server instance using --admin-only flag > 2. Deploy application using CLI command. > ~~~ > deploy /valid/path/WebApp.war --runtime-name=WebApp.war --name=WebApp.war > ~~~ > 3. Undeploy application using CLI command: > ~~~ > undeploy WebApp.war > ~~~ > 4. Application will be undeployed but content from 'data' directory are not removed. > {noformat} > Lines: > https://github.com/wildfly/wildfly-core/blob/b1a4439f442f7984e681840c0f8d... > https://github.com/wildfly/wildfly-core/blob/e737eff554ee433ca54835154fd6... > runningMode value is ADMIN_ONLY will bypass that step in DeploymentRemoveHandler.java leads to this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-457) SASL SAML Authentication Mechanism

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-457?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-457: -------------------------------- Added analysis document > SASL SAML Authentication Mechanism > ---------------------------------- > > Key: ELY-457 > URL: https://issues.jboss.org/browse/ELY-457 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > https://tools.ietf.org/html/rfc6595 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9589) Upgrade JBossXACML to 2.0.10

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-9589?page=com.atlassian.jira.plugin.... ] Yeray Borges moved JBEAP-13894 to WFLY-9589: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9589 (was: JBEAP-13894) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade JBossXACML to 2.0.10 > ---------------------------- > > Key: WFLY-9589 > URL: https://issues.jboss.org/browse/WFLY-9589 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: Yeray Borges > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1960) Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1960?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1960: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING > -------------------------------------------------------------------- > > Key: WFCORE-1960 > URL: https://issues.jboss.org/browse/WFCORE-1960 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Fix For: 4.0.0.Alpha5 > > Attachments: rrd.txt > > > A read-resource-description output of a standalone-full-ha.xml server (see attached) shows a couple attributes that are of type LIST, value-type PROPERTY. (Just text search for PROPERTY.) We should convert those to OBJECT, value-type STRING. Both represent a resource address. An object of string is equivalent to a LinkedHashMap<String, String>, with ordering based on insertion. So such a description is fine for a path address attribute. > I'd like to get rid of the notion of PROPERTY in our spec definition of how to describe attributes, parameters and value-types (https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...) so removing the only usage of it will help. > We should still accept PROPERTY as inputs when we can do conversion to the defined type. This is all about tightening up the spec to remove the not-really-necessary PROPERTY concept. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1944) Convert domain-management tests to reference Elytron SecurityRealm and remove old CallbackHandler code.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1944?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1944: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Convert domain-management tests to reference Elytron SecurityRealm and remove old CallbackHandler code. > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1944 > URL: https://issues.jboss.org/browse/WFCORE-1944 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha5 > > > The important pieces of code within the legacy security realms are being wrapped using Elytron components, items like the legacy CallbackHandlers can be removed but existing tests need porting to call Elytron APIs. > The legacy tests do need to be retained as they offer a good level of regression testing for the legacy realms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1649) RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1649?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1649: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1649 > URL: https://issues.jboss.org/browse/WFCORE-1649 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Labels: domain-mode > Fix For: 4.0.0.Alpha5 > > > The management model for RBAC constraints is maintained using synthetic resources, with resources only existing for those items (SensitivityClassification and ApplicationClassification) that are registered in the current process. Operations that touch classifications unknown to that process will fail due to missing resource problems. > This is a big problem in the following scenarios: > 1) Mixed domain, where legacy slaves do not know about newly introduced classifications. > 2) Slimming scenarios where slaves are ignoring unrelated parts of the domain wide config and also don't have some extension installed, resulting in classifications registered by those extensions not being present. > A partial workaround to 1) is for the kernel to register transformers for newly introduced classifications (e.g. SERVER_SSL added in EAP 6.4.7 and EAP 7). But: > -- that doesn't help with problem 2) > -- only the kernel can register kernel transformers, so if extensions add new classifications there is no way for them to register the transformer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1489) Expose (un)registerNotificationHandler() on OperationContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1489?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1489: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Expose (un)registerNotificationHandler() on OperationContext > ------------------------------------------------------------ > > Key: WFCORE-1489 > URL: https://issues.jboss.org/browse/WFCORE-1489 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Fix For: 4.0.0.Alpha5 > > > Currently the only way to (un)register notifications is via the NotificationHandlerRegistration exposed by ModelController.getNotificationRegistry(). It would be nice to not have to install a service whose only purpose is to get hold of the ModelController from OSH's. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017