August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3952) Unable to run -DallTests -Delytron builds

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3952?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3952: ------------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.0.CR2) > Unable to run -DallTests -Delytron builds > ----------------------------------------- > > Key: WFCORE-3952 > URL: https://issues.jboss.org/browse/WFCORE-3952 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.0.0.Alpha1 > > > Attempting to use -DallTests -Delytron results in the following error: - > {noformat} > [ERROR] } > [ERROR] Cannot start embedded Host Controller: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYHC0097: Domain base directory does not exist: /home/darranl/src/wildfly13/wildfly-core/testsuite/standalone/target/wildfly-core/domain > {noformat} > I believe this is actually caused by WFCORE-3769 which provisions a standalone server only. > We don't currently run -Delytron jobs for WildFly Core but this bug causes problems with experimental builds where we may want to use -Delytron. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2897) Use test category for new and legacy test scenarios

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2897: ------------------------------------ Summary: Use test category for new and legacy test scenarios Key: DROOLS-2897 URL: https://issues.jboss.org/browse/DROOLS-2897 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing, Test Scenarios Editor Reporter: Toni Rikkola Assignee: Daniele Zonca -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1409) Update HTTP authentication mechanism API to support re-use of response handlers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1409?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1409: ---------------------------------- Fix Version/s: 1.7.0.CR1 (was: 1.5.6.CR1) > Update HTTP authentication mechanism API to support re-use of response handlers > ------------------------------------------------------------------------------- > > Key: ELY-1409 > URL: https://issues.jboss.org/browse/ELY-1409 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR1 > > > At the moment the response handler can only access the response, it can not access anything from the request unless created with access to the request. > Making the scopes available should allow for state to be transferred on the request scope. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1637) Change ReferralMode.toString to return value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1637?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1637: ---------------------------------- Fix Version/s: 1.7.0.CR1 > Change ReferralMode.toString to return value > -------------------------------------------- > > Key: ELY-1637 > URL: https://issues.jboss.org/browse/ELY-1637 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Philippe Marschall > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR1 > > > The documentation of the referral-mode attribute in WildFly says the allowed values should be "ignore", "follow", "throw". However they are currently serialized as "IGNORE", "FOLLOW", "THROW". This is a WildFly issue and not an Elytron issue. > However as part of the discussion on how to best fix WFCORE-3971 the easiest solution seems to be to change {{ReferralMode#toString()}}, that way the parser does not have to change. > Once WildFly upgrades to a version of Elytron with this change a couple of tests will fail as the serialized model will intentionally change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4048) Unable to configure custom security realm in deployment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4048?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4048: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Unable to configure custom security realm in deployment > ------------------------------------------------------- > > Key: WFCORE-4048 > URL: https://issues.jboss.org/browse/WFCORE-4048 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 6.0.0.CR2 > Reporter: Martin Choma > > Original user report [1]: > Hello everyone, I am migrating from legacy security to Elytron, and I have a problem. Is there anyone who can help me? We have a custom login-module that queries infinispan cache (which maps simple bearer tokens to user names), and then queries the database (to get user roles), and on commit essentially wraps it up in Principal object. Elytron doesn't have login-modules, but security realms. There is no default realm that matches our desired functionality, so we need to define a new custom-realm. The problem is, security realms can be defined with classes in wildfly "modules", not deployments. And since "modules" can't contain EJB's, I can't inject neither infinispan cache nor database entity manager in the code. Please help what is the right way to go here > I was thinking about it and I have come to conclusion that Elytron is not able to do the same as legacy. I assume that user is right that you cant use EE features in modules. And it looks to me Elytorn does not allow dependency on deployment module. Because Elytron checks existance of module in time of starting and deployment can be not loaded yet. In legacy existance verification is apparently postponed to time of usage. > So I assume in legacy you can define custom login module in deployment (with EE annotations) and register such login module in security subsystem. And dependencies are resolved in runtime and not in boottime. > [1] https://wildfly.hipchat.com/embedded/history/room/699248/2018/07/18?p=1&q... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10877) Jaeger-thrift jar dependency is quite chubby

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/WFLY-10877?page=com.atlassian.jira.plugin... ] Juraci Paixão Kröhling updated WFLY-10877: ------------------------------------------ Git Pull Request: (was: https://github.com/jaegertracing/jaeger-client-java/pull/526) > Jaeger-thrift jar dependency is quite chubby > -------------------------------------------- > > Key: WFLY-10877 > URL: https://issues.jboss.org/browse/WFLY-10877 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Reporter: Jan Stourac > Assignee: Juraci Paixão Kröhling > > Jaeger-thrift dependency file is quite chubby: > {code} > -rw-rw-r--. 1 jstourac jstourac 123K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-core-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 2.8M Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > {code} > Is there any possibility to shrink it's size somehow? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10877) Jaeger-thrift jar dependency is quite chubby

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/WFLY-10877?page=com.atlassian.jira.plugin... ] Juraci Paixão Kröhling commented on WFLY-10877: ----------------------------------------------- Upstream PR: https://github.com/jaegertracing/jaeger-client-java/pull/526 > Jaeger-thrift jar dependency is quite chubby > -------------------------------------------- > > Key: WFLY-10877 > URL: https://issues.jboss.org/browse/WFLY-10877 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Reporter: Jan Stourac > Assignee: Juraci Paixão Kröhling > > Jaeger-thrift dependency file is quite chubby: > {code} > -rw-rw-r--. 1 jstourac jstourac 123K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-core-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 2.8M Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > {code} > Is there any possibility to shrink it's size somehow? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4051) KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4051?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4051: ------------------------------------- Fix Version/s: 6.0.0.CR3 > KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used > ------------------------------------------------------------------------- > > Key: WFCORE-4051 > URL: https://issues.jboss.org/browse/WFCORE-4051 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 6.0.0.CR2 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 6.0.0.CR3 > > > Creating 2-way SSL Context fails with error. > {code} > 12:04:28,689 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.ssl-context.ssl-context-client-cert: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssl-context-client-cert: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used > at sun.security.ssl.SSLContextImpl.chooseTrustManager(SSLContextImpl.java:115) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:78) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980) > ... 9 more > 12:04:28,690 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-context" => "ssl-context-client-cert") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssl-context-client-cert" => "java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used"}} > {code} > Seems DelegatingTrustManager is created always. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10847) Multiple service modules in single EAR use same tracer instance

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/WFLY-10847?page=com.atlassian.jira.plugin... ] Juraci Paixão Kröhling updated WFLY-10847: ------------------------------------------ Sprint: Kiali Sprint #9, Kiali Sprint #10 (was: Kiali Sprint #9) > Multiple service modules in single EAR use same tracer instance > --------------------------------------------------------------- > > Key: WFLY-10847 > URL: https://issues.jboss.org/browse/WFLY-10847 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Reporter: Michal Jurc > Assignee: Juraci Paixão Kröhling > Priority: Blocker > Fix For: 14.0.0.CR1 > > > When deploying an EAR with two stand-alone JAX-RS services in stand-alone WAR modules, both of the services use the same {{Tracer}} instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10890) CLI client in jconsole doesn't work with JDK11

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-10890?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFLY-10890: --------------------------------- Labels: Java11 blocker-WF14 (was: ) > CLI client in jconsole doesn't work with JDK11 > ---------------------------------------------- > > Key: WFLY-10890 > URL: https://issues.jboss.org/browse/WFLY-10890 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Kabir Khan > Priority: Blocker > Labels: Java11, blocker-WF14 > > CLI client in jconsole doesn't work with JDK11. > JConsole uses CLI. CLI uses WildFlySecurityManager (Elytron 1.5.4.Final). WildFlySecurityManager uses sun.misc.Unsafe. Unsafe works just with adding of {{--add-modules=jdk.unsupported}} to JConsole: > {code:diff} > --- a/jconsole.sh > +++ b/jconsole.sh > @@ -79,4 +79,4 @@ CLASSPATH=$CLASSPATH:./bin/client/jboss-cli-client.jar > echo CLASSPATH $CLASSPATH > > cd "$JBOSS_HOME" > -$JAVA_HOME/bin/jconsole -J-Djava.class.path="$CLASSPATH" "$@" > +$JAVA_HOME/bin/jconsole -J--add-modules=jdk.unsupported -J-Djava.class.path="$CLASSPATH" "$@" > \ No newline at end of file > {code} > But "jdk.unsupported" module is not a correct fix. > *Logs:* > {noformat} > Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: sun/misc/Unsafe > at org.wildfly.security.manager.WildFlySecurityManager.<clinit>(WildFlySecurityManager.java:122) > at org.jboss.as.cli.CommandContextFactory.getInstance(CommandContextFactory.java:41) > at org.jboss.as.cli.gui.ConnectDialog$2.actionPerformed(ConnectDialog.java:182) > at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) > at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) > at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) > at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) > at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279) > at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297) > at java.desktop/java.awt.Component.processMouseEvent(Component.java:6631) > at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) > at java.desktop/java.awt.Component.processEvent(Component.java:6396) > at java.desktop/java.awt.Container.processEvent(Container.java:2263) > at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) > at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) > at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) > at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) > at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) > at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) > at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) > at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) > at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) > at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) > at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) > Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 39 more > {noformat} > *cc:* [~kabirkhan], [~jamezp], [~darranl], [~mchoma], [~msvehla], [~okotek] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 2018