June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2963) Management/security-realm/authentication/users integration with credential reference is not correct.

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2963?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2963: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Darran Lofthouse) > Management/security-realm/authentication/users integration with credential reference is not correct. > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-2963 > URL: https://issues.jboss.org/browse/WFCORE-2963 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: ehsavoie Hugonnet > Priority: Blocker > > Management/security-realm/authentication/users integration with credential reference is not correct. > When user set authentication/users instead of authentication/properties and add there user who has defined credential-reference then he is not able to log in to management console. > It must work, please check *Steps to Reproduce* section. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8742) Elytron programmatic AuthenticationContext configuration doesn't work for naming client

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8742?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFLY-8742: ------------------------------------ AS TS test issue fix https://github.com/wildfly/wildfly/pull/10200 > Elytron programmatic AuthenticationContext configuration doesn't work for naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-8742 > URL: https://issues.jboss.org/browse/WFLY-8742 > Project: WildFly > Issue Type: Bug > Components: Naming, Security > Reporter: Josef Cacek > Assignee: David Lloyd > Priority: Blocker > > Naming client doesn't handle correctly the Elytron AuthenticationContext API. > * if the API is used then authentication fails (SASL mech is not configured as expected) - it fails in both cases: wildfly-config.xml present or not. > {code:java} > AuthenticationContext.empty() > .with(MatchRule.ALL, AuthenticationConfiguration.EMPTY.useDefaultProviders().allowSaslMechanisms("ANONYMOUS")) > .run(() -> { > doLookup("http-remoting://127.0.0.1:8080"); > }); > {code} > * if the API is not used and wildfly-config.xml is present, then the client works correctly > {code:java} > doLookup("http-remoting://127.0.0.1:8080"); > {code} > {code:xml} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="authn" /> > </authentication-rules> > <authentication-configurations> > <configuration name="authn"> > <allow-sasl-mechanisms names="ANONYMOUS"/> > <use-service-loader-providers /> > </configuration> > </authentication-configurations> > </authentication-client> > </configuration> > {code} > This blocks RFEs EAP7-567 and EAP7-284. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8742) Elytron programmatic AuthenticationContext configuration doesn't work for naming client

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8742?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-8742: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10200 > Elytron programmatic AuthenticationContext configuration doesn't work for naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-8742 > URL: https://issues.jboss.org/browse/WFLY-8742 > Project: WildFly > Issue Type: Bug > Components: Naming, Security > Reporter: Josef Cacek > Assignee: David Lloyd > Priority: Blocker > > Naming client doesn't handle correctly the Elytron AuthenticationContext API. > * if the API is used then authentication fails (SASL mech is not configured as expected) - it fails in both cases: wildfly-config.xml present or not. > {code:java} > AuthenticationContext.empty() > .with(MatchRule.ALL, AuthenticationConfiguration.EMPTY.useDefaultProviders().allowSaslMechanisms("ANONYMOUS")) > .run(() -> { > doLookup("http-remoting://127.0.0.1:8080"); > }); > {code} > * if the API is not used and wildfly-config.xml is present, then the client works correctly > {code:java} > doLookup("http-remoting://127.0.0.1:8080"); > {code} > {code:xml} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="authn" /> > </authentication-rules> > <authentication-configurations> > <configuration name="authn"> > <allow-sasl-mechanisms names="ANONYMOUS"/> > <use-service-loader-providers /> > </configuration> > </authentication-configurations> > </authentication-client> > </configuration> > {code} > This blocks RFEs EAP7-567 and EAP7-284. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1515) Unable to install feature droolsjbpm-hibernate in Fuse

by Lukáš Petrovický (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1515?page=com.atlassian.jira.plugi... ] Lukáš Petrovický updated DROOLS-1515: ------------------------------------- Fix Version/s: 7.1.0.Final > Unable to install feature droolsjbpm-hibernate in Fuse > ------------------------------------------------------ > > Key: DROOLS-1515 > URL: https://issues.jboss.org/browse/DROOLS-1515 > Project: Drools > Issue Type: Bug > Components: integration > Affects Versions: 7.0.0.Beta8 > Environment: JBOSS Fuse 6.2.1 > JBOSS Fuse 6.3.0 > Reporter: Lubomir Terifaj > Assignee: Mario Fusco > Labels: reported-by-qe > Fix For: 7.1.0.Final > > > Installation of droolsjbpm-hibernate fails with error: > Error executing command: Could not start bundle wrap:mvn:org.hibernate/hibernate-entitymanager/5.1.4.Final$overwrite=merge&DynamicImport-Package=* in feature(s) droolsjbpm-hibernate-5.1.4.Final: Unresolved constraint in bundle org.hibernate.entitymanager [309]: Unable to resolve 309.0: missing requirement [309.0] osgi.wiring.package; (&(osgi.wiring.package=javax.persistence)(version>=2.1.0)) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1487) Parallel agenda cycles itself or throws NPE

by Lukáš Petrovický (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1487?page=com.atlassian.jira.plugi... ] Lukáš Petrovický updated DROOLS-1487: ------------------------------------- Fix Version/s: 7.1.0.Final > Parallel agenda cycles itself or throws NPE > ------------------------------------------- > > Key: DROOLS-1487 > URL: https://issues.jboss.org/browse/DROOLS-1487 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta7 > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Labels: parallel-agenda, reported-by-qe > Fix For: 7.1.0.Final > > > Running AdvOperatorsExpertBenchmark benchmarks from our kie-benchmarks suite with parallel agenda option, the benchmark either cycles itself or throws NPE [1]. I created a "reproducer" here[2]. Be aware that this is failing nondeterministically, so with high probability it is a nasty race condition. > I tried to debug this a bit and this is the output of some variables that is available on this line [3]: > Returned fire count: 0 > Head: null > Group: AgendaGroup 'MAIN' > Group is auto deactivate: true > Limit reached: false > IsInternalFire: false > IsFiring: true > [1] http://pastebin.com/sjLjQwgX > [2] https://github.com/kiegroup/kie-benchmarks/pull/8/files > [3] https://github.com/kiegroup/drools/blob/3038a1b9287978069bcb2765dc684f696... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

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

by Lukáš Petrovický (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ] Lukáš Petrovický updated DROOLS-1511: ------------------------------------- Fix Version/s: 7.1.0.Final > 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: DevStudio 10 + IS 10.3.0.CR2 > Eclipse Neon + Drools plugin 7.0.0.CR3 > Drools Runtime 7.x > Reporter: Tomas David > Assignee: Kris Verlaenen > Priority: Blocker > Labels: reported-by-qe > Fix For: 7.1.0.Final > > > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2368) Missing default value of filter-name in Elytron ldap-realm in management model

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2368?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-2368: ------------------------------------ Assignee: Yeray Borges (was: Darran Lofthouse) > Missing default value of filter-name in Elytron ldap-realm in management model > ------------------------------------------------------------------------------ > > Key: WFCORE-2368 > URL: https://issues.jboss.org/browse/WFCORE-2368 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Ondrej Lukas > Assignee: Yeray Borges > Labels: user_experience > Fix For: 4.0.0.Alpha1 > > > Elytron {{ldap-realm.identity-mapping.filter-name}} attribute has not assigned default value in CLI. However according to XSD it has default value (rdn-identifier={0}). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2172) Non-blocking flow control

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on JGRP-2172: ------------------------------------ +1 for Radim's proposal. The synchronization currently used in {{Credit}} also maintains a queue of waiting threads internally, so this shouldn't impact performance for applications that don't use {{NB_FC}}. > Non-blocking flow control > ------------------------- > > Key: JGRP-2172 > URL: https://issues.jboss.org/browse/JGRP-2172 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.4 > > > Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set. > Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded). The max queue size is given in bytes, so we can estimate what the memory penalty for reaching that size would be (if bounded). > The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first? > Non-blocking flow control can be used by both external and internal threads. > If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2963) Management/security-realm/authentication/users integration with credential reference is not correct.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2963?page=com.atlassian.jira.plugi... ] Hynek Švábek moved WFLY-8937 to WFCORE-2963: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2963 (was: WFLY-8937) Component/s: Security (was: Security) > Management/security-realm/authentication/users integration with credential reference is not correct. > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-2963 > URL: https://issues.jboss.org/browse/WFCORE-2963 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > > Management/security-realm/authentication/users integration with credential reference is not correct. > When user set authentication/users instead of authentication/properties and add there user who has defined credential-reference then he is not able to log in to management console. > It must work, please check *Steps to Reproduce* section. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8937) Management/security-realm/authentication/users integration with credential reference is not correct.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8937?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-8937: ---------------------------------------- All of the resources listed in the steps to reproduce are in WildFly Core, can you please move this Jira to the WFCORE project. > Management/security-realm/authentication/users integration with credential reference is not correct. > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-8937 > URL: https://issues.jboss.org/browse/WFLY-8937 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > > Management/security-realm/authentication/users integration with credential reference is not correct. > When user set authentication/users instead of authentication/properties and add there user who has defined credential-reference then he is not able to log in to management console. > It must work, please check *Steps to Reproduce* section. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017