August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-619) Add a method to SecurityIdentity that sets the security identity for additional domains prior to running an action

by Farah Juma (JIRA)

Farah Juma created ELY-619: ------------------------------ Summary: Add a method to SecurityIdentity that sets the security identity for additional domains prior to running an action Key: ELY-619 URL: https://issues.jboss.org/browse/ELY-619 Project: WildFly Elytron Issue Type: Feature Request Components: API / SPI Reporter: Farah Juma Assignee: Farah Juma This method can be used for identity outflow to set up the security identity for additional domains prior to running an action. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1725) standalone.bat is unable to start with specific debug port & gc logging doesn't log to file

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1725?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved JBEAP-5703 to WFCORE-1725: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1725 (was: JBEAP-5703) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Scripts (was: Scripts) Affects Version/s: 3.0.0.Alpha5 (was: 7.1.0.DR3) Affects Testing: (was: Regression) > standalone.bat is unable to start with specific debug port & gc logging doesn't log to file > ------------------------------------------------------------------------------------------- > > Key: WFCORE-1725 > URL: https://issues.jboss.org/browse/WFCORE-1725 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha5 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > > * standalone.bat is unable to start on Windows with specific debug port > * priority of this jira is blocker because this is regression against 7.0.0.GA > * It may relates with JBEAP-5374 and JBEAP-5551 (CC: Petr Sakař) > {noformat} > C:\Users\Administrator\playground\7.1.0.DR3\jboss-eap-7.1\bin>standalone.bat --debug 7878 > Calling "C:\Users\Administrator\playground\7.1.0.DR3\jboss-eap-7.1\bin\standalone.conf.bat" > Setting JAVA property to "C:\jdk1.8.0_45\bin\java" > "-Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djbo > ss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address="7878,server=y,suspend=n" | findstr /I \-serve > r > nul > "-Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djbo > ss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address="7878,server=y,suspend=n" | findstr /I "\-verb > ose:gc" > nul > =============================================================================== > JBoss Bootstrap Environment > JBOSS_HOME: "C:\Users\Administrator\playground\7.1.0.DR3\jboss-eap-7.1" > JAVA: "C:\jdk1.8.0_45\bin\java" > JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogF > ileSize=3M -Xloggc: -XX:-TraceClassUnloading -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSiz > e=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address="7 > 878,server=y,suspend=n" > =============================================================================== > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > ERROR: JDWP option syntax error: -agentlib:jdwp=transport=dt_socket,address=7878,server=y,suspend=n ^ > The filename, directory name, or volume label syntax is incorrect. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-790) CLI Does Not Log History With "--file" and "--command(s)" args

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-790?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-790: ------------------------------------------------ Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1232890|https://bugzilla.redhat.com/show_bug.cgi?id=1232890] from ASSIGNED to NEW > CLI Does Not Log History With "--file" and "--command(s)" args > --------------------------------------------------------------- > > Key: WFCORE-790 > URL: https://issues.jboss.org/browse/WFCORE-790 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 2.0.0.Alpha5 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > > Cli doesn't log commands passed by "\-\-file" and "\-\-command(s)" arguments. > https://bugzilla.redhat.com/show_bug.cgi?id=1232890 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1247) ForceEagerActivationOption may cause a recursive segment initialization

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1247?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1247: ------------------------------------- Partial fix also cherry-picked to 6.5.x branch with https://github.com/droolsjbpm/drools/commit/4a64e4d56 > ForceEagerActivationOption may cause a recursive segment initialization > ----------------------------------------------------------------------- > > Key: DROOLS-1247 > URL: https://issues.jboss.org/browse/DROOLS-1247 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Beta1, 7.0.0.Beta1 > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Blocker > > ForceEagerActivationOption may cause a recursive segments initialization resulting in an infinite recursive linked list of segment memories like: smem1 -> smem2 -> smem1 -> ... When this happens the segments evaluation makes the engine to fall in an endless loop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6980) Refactor "impl" package in compensations module to "internal"

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6980?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-6980: --------------------------------------- Pull request on Narayana cloned repo: https://github.com/jbosstm/jboss-as/pull/50 > Refactor "impl" package in compensations module to "internal" > ------------------------------------------------------------- > > Key: WFLY-6980 > URL: https://issues.jboss.org/browse/WFLY-6980 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6980) Refactor "impl" package in compensations module to "internal"

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-6980: ------------------------------------- Summary: Refactor "impl" package in compensations module to "internal" Key: WFLY-6980 URL: https://issues.jboss.org/browse/WFLY-6980 Project: WildFly Issue Type: Task Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1247) ForceEagerActivationOption may cause a recursive segment initialization

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1247?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1247: ---------------------------------- Affects Version/s: 7.0.0.Beta1 6.5.0.Beta1 > ForceEagerActivationOption may cause a recursive segment initialization > ----------------------------------------------------------------------- > > Key: DROOLS-1247 > URL: https://issues.jboss.org/browse/DROOLS-1247 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Beta1, 7.0.0.Beta1 > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Blocker > > ForceEagerActivationOption may cause a recursive segments initialization resulting in an infinite recursive linked list of segment memories like: smem1 -> smem2 -> smem1 -> ... When this happens the segments evaluation makes the engine to fall in an endless loop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1619) Bad artifact resolution in wildfly-logging module

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1619?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1619: ------------------------------------- What ware you using? just mvn test? Tested locally and on few other machines, mvn package is enough, install is not needed. > Bad artifact resolution in wildfly-logging module > ------------------------------------------------- > > Key: WFCORE-1619 > URL: https://issues.jboss.org/browse/WFCORE-1619 > Project: WildFly Core > Issue Type: Bug > Components: Logging, Test Suite > Reporter: Carlo de Wolf > Assignee: Tomaz Cerar > Priority: Minor > > The test doesn't use project artifact resolution, but global artifact resolution. While the project hasn't been published yet. > {noformat} > Tests run: 14, Failures: 0, Errors: 6, Skipped: 3, Time elapsed: 21.024 sec <<< FAILURE! - in org.jboss.as.logging.LoggingSubsystemTestCase > testTransformersEAP620(org.jboss.as.logging.LoggingSubsystemTestCase) Time elapsed: 8.508 sec <<< ERROR! > java.lang.RuntimeException: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.wildfly.core:wildfly-subsystem-test-framework:jar:2.1.6.Final-redhat-SNAPSHOT in product-repository (https://maven.repository.redhat.com/nexus/content/groups/product-techprev...) > at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:39) > at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581) > at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) > at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) > at org.jboss.as.model.test.MavenUtil.createMavenGavURL(MavenUtil.java:138) > at org.jboss.as.model.test.ChildFirstClassLoaderBuilder.addMavenResourceURL(ChildFirstClassLoaderBuilder.java:197) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.install(SubsystemTestDelegate.java:839) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.access$700(SubsystemTestDelegate.java:724) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.build(SubsystemTestDelegate.java:691) > at org.jboss.as.logging.LoggingSubsystemTestCase.testEapTransformer(LoggingSubsystemTestCase.java:281) > at org.jboss.as.logging.LoggingSubsystemTestCase.testTransformersEAP620(LoggingSubsystemTestCase.java:130) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-952) AdvancedLdapLoginModule with roleAttributeID="" and empty or unset roleFilter can lead to authentication failure

by Ondrej Lukas (JIRA)

Ondrej Lukas created SECURITY-952: ------------------------------------- Summary: AdvancedLdapLoginModule with roleAttributeID="" and empty or unset roleFilter can lead to authentication failure Key: SECURITY-952 URL: https://issues.jboss.org/browse/SECURITY-952 Project: PicketBox Issue Type: Bug Reporter: Ondrej Lukas Assignee: Stefan Guilhen In case when AdvancedLdapLoginModule is correctly configured for authentication, but its attribute roleAttributeID is empty string and roleFilter is not set (i.e. is null) or roleFilter is empty string, then authentication with correct username and password fails. It is caused by internal NPE for searching roles. Expected behavior is that users should be authenticated but no roles should be assigned to them. Internal NPE: {code} java.lang.NullPointerException at org.jboss.security.negotiation.AdvancedLdapLoginModule.obtainRole(AdvancedLdapLoginModule.java:821) at org.jboss.security.negotiation.AdvancedLdapLoginModule.rolesSearch(AdvancedLdapLoginModule.java:762) at org.jboss.security.negotiation.AdvancedLdapLoginModule.innerLogin(AdvancedLdapLoginModule.java:412) at org.jboss.security.negotiation.AdvancedLdapLoginModule$AuthorizeAction.run(AdvancedLdapLoginModule.java:981) at org.jboss.security.negotiation.AdvancedLdapLoginModule.login(AdvancedLdapLoginModule.java:331) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-952) AdvancedLdapLoginModule with roleAttributeID="" and empty or unset roleFilter can lead to authentication failure

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/SECURITY-952?page=com.atlassian.jira.plug... ] Ondrej Lukas updated SECURITY-952: ---------------------------------- Affects Version/s: Negotiation_3_0_3_Final > AdvancedLdapLoginModule with roleAttributeID="" and empty or unset roleFilter can lead to authentication failure > ---------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-952 > URL: https://issues.jboss.org/browse/SECURITY-952 > Project: PicketBox > Issue Type: Bug > Affects Versions: Negotiation_3_0_3_Final > Reporter: Ondrej Lukas > Assignee: Stefan Guilhen > > In case when AdvancedLdapLoginModule is correctly configured for authentication, but its attribute roleAttributeID is empty string and roleFilter is not set (i.e. is null) or roleFilter is empty string, then authentication with correct username and password fails. It is caused by internal NPE for searching roles. > Expected behavior is that users should be authenticated but no roles should be assigned to them. > Internal NPE: > {code} > java.lang.NullPointerException > at org.jboss.security.negotiation.AdvancedLdapLoginModule.obtainRole(AdvancedLdapLoginModule.java:821) > at org.jboss.security.negotiation.AdvancedLdapLoginModule.rolesSearch(AdvancedLdapLoginModule.java:762) > at org.jboss.security.negotiation.AdvancedLdapLoginModule.innerLogin(AdvancedLdapLoginModule.java:412) > at org.jboss.security.negotiation.AdvancedLdapLoginModule$AuthorizeAction.run(AdvancedLdapLoginModule.java:981) > at org.jboss.security.negotiation.AdvancedLdapLoginModule.login(AdvancedLdapLoginModule.java:331) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016