[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)
3 years, 8 months
[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)
3 years, 8 months
[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)
3 years, 8 months