May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8741) Elytron credential-store should offer operations instead of alias resource

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8741?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-8741: ----------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly/pull/202 (was: https://github.com/wildfly/wildfly/pull/10037) > Elytron credential-store should offer operations instead of alias resource > -------------------------------------------------------------------------- > > Key: WFLY-8741 > URL: https://issues.jboss.org/browse/WFLY-8741 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Elytron credential-store resources should offer operations instead of alias resource, as for key-stores, as it can be based on any key-store too. > The reason is more described in WFCORE-2691 or related mailing thread on wildfly-dev. > Setting priority to blocker by WFCORE-2691 and WFCORE-2737. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2805) Use Xalan from JRE rather than our own fork

by Peter Palaga (JIRA)

Peter Palaga created WFCORE-2805: ------------------------------------ Summary: Use Xalan from JRE rather than our own fork Key: WFCORE-2805 URL: https://issues.jboss.org/browse/WFCORE-2805 Project: WildFly Core Issue Type: Task Reporter: Peter Palaga Assignee: Peter Palaga As proposed by [~wolfc] we want to check if we can get rid of maintaining our own fork of Xalan. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2730) empty target-name in constant-permission-mapper is not allowed

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2730?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-2730: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2419 > empty target-name in constant-permission-mapper is not allowed > -------------------------------------------------------------- > > Key: WFCORE-2730 > URL: https://issues.jboss.org/browse/WFCORE-2730 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Eva Jarkovská > Assignee: Jan Kalina > Fix For: 3.0.0.Beta22 > > > For some purposes there is need to construct permission with blank string as param (name/action) - for example *WebResourcePermission*. > Such permission cannot be currently assigned using *constant-permission-mapper* because it requires at least one character to be not-null: > If I try to assing permission with blank name ({{target-name=""}}) (example in steps to reproduce), parse error is thrown: > {code} > | > ParseError at [row,col]:[367,5] > | > Message: "WFLYCTL0113: '' is an invalid value for parameter > | > target-name. Values must have a minimum length of 1 characters" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2804) Elytron key-managers: operations do not reflect alias-filter attribute

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2804?page=com.atlassian.jira.plugi... ] Ondrej Kotek updated WFCORE-2804: --------------------------------- Description: Operations {{add}} and {{write-attribute}} of Elytron {{key-managers}} do not reflect {{alias-filter}} attribute, see steps to reproduce. (was: Operations {{add}} and {{write-attribute}} of Elytron key-manager do not reflect alias-filter attribute, see steps to reproduce.) > Elytron key-managers: operations do not reflect alias-filter attribute > ---------------------------------------------------------------------- > > Key: WFCORE-2804 > URL: https://issues.jboss.org/browse/WFCORE-2804 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta21 > Reporter: Ondrej Kotek > > Operations {{add}} and {{write-attribute}} of Elytron {{key-managers}} do not reflect {{alias-filter}} attribute, see steps to reproduce. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2804) Elytron key-managers: operations do not reflect alias-filter attribute

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2804?page=com.atlassian.jira.plugi... ] Ondrej Kotek updated WFCORE-2804: --------------------------------- Summary: Elytron key-managers: operations do not reflect alias-filter attribute (was: Elytron key-manager: operations do not reflect alias-filter attribute) > Elytron key-managers: operations do not reflect alias-filter attribute > ---------------------------------------------------------------------- > > Key: WFCORE-2804 > URL: https://issues.jboss.org/browse/WFCORE-2804 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta21 > Reporter: Ondrej Kotek > > Operations {{add}} and {{write-attribute}} of Elytron key-manager do not reflect alias-filter attribute, see steps to reproduce. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2804) Elytron key-manager: operations do not reflect alias-filter attribute

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2804?page=com.atlassian.jira.plugi... ] Ondrej Kotek moved JBEAP-10902 to WFCORE-2804: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2804 (was: JBEAP-10902) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta21 (was: 7.1.0.DR18) > Elytron key-manager: operations do not reflect alias-filter attribute > --------------------------------------------------------------------- > > Key: WFCORE-2804 > URL: https://issues.jboss.org/browse/WFCORE-2804 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta21 > Reporter: Ondrej Kotek > > Operations {{add}} and {{write-attribute}} of Elytron key-manager do not reflect alias-filter attribute, see steps to reproduce. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-1511: ------------------------------------------- [~tomasdavidorg] please specify the version of Drools plugin. Is there any workaround? > NullPointerException when running sample projects > ------------------------------------------------- > > Key: DROOLS-1511 > URL: https://issues.jboss.org/browse/DROOLS-1511 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: 7.0.0-SNAPSHOT > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Blocker > Labels: reported-by-qe > > NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created. > Eclipse log: > !SESSION 2017-04-04 12:39:38.638 ----------------------------------------------- > eclipse.buildId=4.6.3.M20170301-0400 > java.version=1.8.0_121 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737 > !MESSAGE Internal error in Drools Plugin: > !STACK 1 > Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'] > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112) > at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122) > at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739 > !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1560) Simplify and improve performances of ChainedProperties discovery

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1560?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1560: ------------------------------------- Documented by https://github.com/kiegroup/kie-docs/commit/c082aa4d493558863dcbf4f163dd0... > Simplify and improve performances of ChainedProperties discovery > ---------------------------------------------------------------- > > Key: DROOLS-1560 > URL: https://issues.jboss.org/browse/DROOLS-1560 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2803) Unify default wildfly-config.xml across clients (Elytron)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2803?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-10900 to WFCORE-2803: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2803 (was: JBEAP-10900) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR11) Fix Version/s: 3.0.0.Beta22 (was: 7.1.0.DR18) > Unify default wildfly-config.xml across clients (Elytron) > --------------------------------------------------------- > > Key: WFCORE-2803 > URL: https://issues.jboss.org/browse/WFCORE-2803 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: authentication-client, wildfly-config > Fix For: 3.0.0.Beta22 > > > Some client facing JARs contains default Elytron client configuration in `META-INF/wildfly-config.xml`: > {code} > bin/client/jboss-cli-client.jar > bin/client/jboss-client.jar > modules/system/layers/base/org/jboss/as/protocol/main/wildfly-protocol-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/as/remoting/main/wildfly-remoting-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/remoting-jmx/main/remoting-jmx-3.0.0.Beta2-redhat-1.jar > modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-3.0.0.Beta4-redhat-1.jar > {code} > The configuration across the libraries is not unified, which could lead to different configuration used for different classpath ordering. > The issue is mainly with set of allowed SASL mechanisms across the libraries. Here are fragments of mechanism filtering used in the mentioned files: > {code:xml} > <allow-all-sasl-mechanisms /> > <allow-sasl-mechanisms names="JBOSS-LOCAL-USER EXTERNAL DIGEST-MD5 PLAIN ANONYMOUS" /> > <allow-sasl-mechanisms names="JBOSS-LOCAL-USER DIGEST-MD5 PLAIN ANONYMOUS" /> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2803) Remove default wildfly.config.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2803?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2803: ------------------------------------- Summary: Remove default wildfly.config.xml (was: Unify default wildfly-config.xml across clients (Elytron)) > Remove default wildfly.config.xml > ---------------------------------- > > Key: WFCORE-2803 > URL: https://issues.jboss.org/browse/WFCORE-2803 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: authentication-client, wildfly-config > Fix For: 3.0.0.Beta22 > > > Some client facing JARs contains default Elytron client configuration in `META-INF/wildfly-config.xml`: > {code} > bin/client/jboss-cli-client.jar > bin/client/jboss-client.jar > modules/system/layers/base/org/jboss/as/protocol/main/wildfly-protocol-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/as/remoting/main/wildfly-remoting-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-3.0.0.Alpha22-redhat-1.jar > modules/system/layers/base/org/jboss/remoting-jmx/main/remoting-jmx-3.0.0.Beta2-redhat-1.jar > modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-3.0.0.Beta4-redhat-1.jar > {code} > The configuration across the libraries is not unified, which could lead to different configuration used for different classpath ordering. > The issue is mainly with set of allowed SASL mechanisms across the libraries. Here are fragments of mechanism filtering used in the mentioned files: > {code:xml} > <allow-all-sasl-mechanisms /> > <allow-sasl-mechanisms names="JBOSS-LOCAL-USER EXTERNAL DIGEST-MD5 PLAIN ANONYMOUS" /> > <allow-sasl-mechanisms names="JBOSS-LOCAL-USER DIGEST-MD5 PLAIN ANONYMOUS" /> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 May 2017