August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13728) JDR zip directories are files on Windows

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-13728: ----------------------------------- Summary: JDR zip directories are files on Windows Key: WFLY-13728 URL: https://issues.redhat.com/browse/WFLY-13728 Project: WildFly Issue Type: Bug Components: JDR Affects Versions: 20.0.0.Final Reporter: Brad Maxwell Assignee: Brad Maxwell The directory patch separators are wrong when run on Windows causing there to be no directories but file with the directory path in the name. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4985) Upgrade JBoss Invocation from 1.5.3 to 1.6.0

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4985?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4985: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Upgrade JBoss Invocation from 1.5.3 to 1.6.0 > -------------------------------------------- > > Key: WFCORE-4985 > URL: https://issues.redhat.com/browse/WFCORE-4985 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Brian Stansberry > Assignee: Richard Opalka > Priority: Major > Fix For: 13.0.0.Beta4 > > > Tag: [https://github.com/jbossas/jboss-invocation/releases/tag/1.6.0.Final|http...] > Diff to previous integrated release: [https://github.com/jbossas/jboss-invocation/compare/1.5.3.Final... > Pick up enhanced JBINV-9 fix. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5020) Although elytron has module for JACC factory it is not used for JACC

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5020?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5020: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Although elytron has module for JACC factory it is not used for JACC > -------------------------------------------------------------------- > > Key: WFCORE-5020 > URL: https://issues.redhat.com/browse/WFCORE-5020 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 12.0.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > A module can be specified and this is used to load the specified provider class and instantiate it, however this is separate to the one instantiated by PolicyConfigurationFactory. > Elytron does set a system property to ensure the configured class name is used but does not actually ensure the module is used for class loading. > At the same time it should be ensuring there is only a single instance of the class. > Finally we should verify the correct class has been loaded in case some race condition has caused premature initialisation - those can be difficult to debug. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5032) Elytron subsystem should not depend upon PicketBox

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5032?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5032: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Elytron subsystem should not depend upon PicketBox > -------------------------------------------------- > > Key: WFCORE-5032 > URL: https://issues.redhat.com/browse/WFCORE-5032 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 13.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5033) Move org.wildfly.security:wildfly-elytron-jacc into it's own module

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5033?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5033: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Move org.wildfly.security:wildfly-elytron-jacc into it's own module > ------------------------------------------------------------------- > > Key: WFCORE-5033 > URL: https://issues.redhat.com/browse/WFCORE-5033 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > Long term it will be desirable for JACC to be within it's own subsystem so it's inclusion can be controlled using layers, however there may be an intermediate step where we split JACC out from the Elytron project so will want to bring it in ideally in it's own module. > The classes within this module have never been public API so we are free to refactor as needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5040) Elytron JASPI fallback causes dependency on PicketBox

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5040?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5040: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Elytron JASPI fallback causes dependency on PicketBox > ----------------------------------------------------- > > Key: WFCORE-5040 > URL: https://issues.redhat.com/browse/WFCORE-5040 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > The following is logged when PicketBox is not present. > > {code:java} > 2020-07-08 17:35:19,080 TRACE [org.wildfly.extension.elytron] (ServerService Thread Pool -- 16) Unable to load default AuthConfigFactory.: java.lang.IllegalStateException: Failed to find AuthConfigFactory : org.jboss.security.auth.message.config.JBossAuthConfigFactory2020-07-08 17:35:19,080 TRACE [org.wildfly.extension.elytron] (ServerService Thread Pool -- 16) Unable to load default AuthConfigFactory.: java.lang.IllegalStateException: Failed to find AuthConfigFactory : org.jboss.security.auth.message.config.JBossAuthConfigFactory at javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:227) at org.wildfly.extension.elytron.ElytronDefinition.getAuthConfigFactory(ElytronDefinition.java:405) at org.wildfly.extension.elytron.ElytronDefinition.access$700(ElytronDefinition.java:112) at org.wildfly.extension.elytron.ElytronDefinition$ElytronAdd.lambda$performBoottime$0(ElytronDefinition.java:499) at org.wildfly.extension.elytron.SecurityActions.doPrivileged(SecurityActions.java:35) at org.wildfly.extension.elytron.ElytronDefinition$ElytronAdd.performBoottime(ElytronDefinition.java:499) at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:119) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485)Caused by: java.lang.ClassNotFoundException: org.jboss.security.auth.message.config.JBossAuthConfigFactory from [Module "org.wildfly.extension.elytron" version 13.0.0.Beta2-SNAPSHOT from local module loader @5f2108b5 (finder: local module finder @31a5c39e (roots: /home/darranl/tmp/jacc/minimal/modules,/home/darranl/tmp/jacc/minimal/modules/system/layers/base))] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at javax.security.auth.message.config.AuthConfigFactory$LoadAction.run(AuthConfigFactory.java:571) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:211) ... 17 more {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5049) Ensure any java.security.Policy is registered before PolicyConfigurationFactory

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5049?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5049: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > Ensure any java.security.Policy is registered before PolicyConfigurationFactory > ------------------------------------------------------------------------------- > > Key: WFCORE-5049 > URL: https://issues.redhat.com/browse/WFCORE-5049 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > A PolicyConfigurationFactory may want to consult the Policy so ensure it is installed first. > This comes up within the Jakarta EE TCK where the test PolicyConfigurationFactory consults the underlying registered Policy. > https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/... > {code} > 12:11:00,728 ERROR [stderr] (MSC service thread 1-3) java.lang.ClassCastException: org.jboss.modules.ModulesPolicy cannot be cast to com.sun.ts.tests.jacc.provider.TSPolicy > 12:11:00,728 ERROR [stderr] (MSC service thread 1-3) at com.sun.ts.tests.jacc.provider.TSPolicyConfigurationFactoryImpl.getTSLogger(TSPolicyConfigurationFactoryImpl.java:229) > 12:11:00,729 ERROR [stderr] (MSC service thread 1-3) at com.sun.ts.tests.jacc.provider.TSPolicyConfigurationFactoryImpl.getPolicyConfigurationFactory(TSPolicyConfigurationFactoryImpl.java:159) > 12:11:00,729 ERROR [stderr] (MSC service thread 1-3) at com.sun.ts.tests.jacc.provider.TSPolicyConfigurationFactoryImpl.<init>(TSPolicyConfigurationFactoryImpl.java:53) > 12:11:00,729 ERROR [stderr] (MSC service thread 1-3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5076) remoting http-connector silently accepts invalid security-realm

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5076?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5076: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > remoting http-connector silently accepts invalid security-realm > --------------------------------------------------------------- > > Key: WFCORE-5076 > URL: https://issues.redhat.com/browse/WFCORE-5076 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > If the remoting subsystem is changed to the following: > {code:xml} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="OtherRealm"/> > </subsystem> > {code} > The server starts without error, however attempting to establish a connection fails. > {code} > ./jboss-cli.sh -c --controller=remote+http://localhost:8080 > Failed to connect to the controller: The controller is not available at localhost:8080: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:8080. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:8080. The connection failed: Invalid response code 200 > {code} > Although the CLI can not do anything over port 8080 it should be able to initiate a remoting connection i.e. > {code} > ./jboss-cli.sh -c --controller=remote+http://localhost:8080 > Failed to connect to the controller: The controller is not available at localhost:8080: org.jboss.remoting3.ServiceOpenException: Unknown service name management: Unknown service name management > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5078) remoting layer defines no dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5078?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5078: ------------------------------------- Fix Version/s: 13.0.0.Beta4 (was: 13.0.0.Beta3) > remoting layer defines no dependencies > -------------------------------------- > > Key: WFCORE-5078 > URL: https://issues.redhat.com/browse/WFCORE-5078 > Project: WildFly Core > Issue Type: Bug > Components: Build System, Remoting > Affects Versions: 13.0.0.Beta2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > The remoting layer depends upon legacy security realms but this dependency is not defined. > The layer named "remoting" should be updated to reference an elytron sasl-authentication-factory and the layer should depend upon the elytron layer. > There should be a second layer "legacy-remoting" which references the ApplicationRealm security realm and also this layer should have a dependency on the layer "application-security-realm". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13727) Upgrade WildFly Core to 13.0.0.Beta3

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13727?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13727: ------------------------------------ Security: (was: Security Issue) > Upgrade WildFly Core to 13.0.0.Beta3 > ------------------------------------ > > Key: WFLY-13727 > URL: https://issues.redhat.com/browse/WFLY-13727 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12315422&vers... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020