March 2017 - jboss-jira - Jboss List Archives

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2368?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-7610 to WFCORE-2368: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2368 (was: WFLY-7610) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta7 (was: 11.0.0.Alpha1) Fix Version/s: 4.0.0.Alpha1 (was: 11.0.0.Alpha1) > 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: Darran Lofthouse > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2364) User should be able to specify only one password mapper in jdbc-realm resource

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2364?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-7287 to WFCORE-2364: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2364 (was: WFLY-7287) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta7 (was: 11.0.0.Alpha1) > User should be able to specify only one password mapper in jdbc-realm resource > ------------------------------------------------------------------------------ > > Key: WFCORE-2364 > URL: https://issues.jboss.org/browse/WFCORE-2364 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Martin Choma > Assignee: Pedro Igor > Priority: Minor > Labels: user_experience > > It is possible to specify in {{principal-query}} all of {{clear-password-mapper}}, {{bcrypt-mapper}}, {{simple-digest-mapper}}, {{salted-simple-digest-mapper}}, {{scram-mapper}} at one moment. But, in fact, specifying only one mapper per principal query make sense. Change model/subsystem , that only adding on password mapper at a moment is allowed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7081) Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7081?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7081: -------------------------------------- Assignee: Darran Lofthouse (was: Stuart Douglas) > Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true" > ------------------------------------------------------------------------------------------ > > Key: WFLY-7081 > URL: https://issues.jboss.org/browse/WFLY-7081 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > When I want to use HTTPS settings in combination with Elytron subsystem then I have to set "enable-http2" to "false" value. > For settings I followed this blog post http://darranl.blogspot.cz/2016/02/wildfly-elytron-ssl-configuration.html > And as keystore I used default application.keystore -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-994) Add option to SSLContextBuilder to control if resulting SSLEngine is protected.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-994: ------------------------------------ Summary: Add option to SSLContextBuilder to control if resulting SSLEngine is protected. Key: ELY-994 URL: https://issues.jboss.org/browse/ELY-994 Project: WildFly Elytron Issue Type: Enhancement Components: SSL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta29 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8314) EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created WFLY-8314: ------------------------------------- Summary: EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile Key: WFLY-8314 URL: https://issues.jboss.org/browse/WFLY-8314 Project: WildFly Issue Type: Bug Components: XTS Reporter: Ondra Chaloupka Assignee: Gytis Trikleris Priority: Critical When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged: {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "undertow"), ("server" => "default-server"), ("host" => "default-host"), ("setting" => "http-invoker") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"] } 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker] 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand) {code} This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services in standalone-xts and standalone-rts profile

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated WFLY-8314: ---------------------------------- Summary: WFLY starts with errors and missing services in standalone-xts and standalone-rts profile (was: EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile) > WFLY starts with errors and missing services in standalone-xts and standalone-rts profile > ----------------------------------------------------------------------------------------- > > Key: WFLY-8314 > URL: https://issues.jboss.org/browse/WFLY-8314 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > Priority: Critical > > When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged: > {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("host" => "default-host"), > ("setting" => "http-invoker") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"] > } > 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker] > 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server > 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand) > {code} > This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services in standalone-xts and standalone-rts profile

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned WFLY-8314: ------------------------------------- Assignee: Ondra Chaloupka (was: Gytis Trikleris) > WFLY starts with errors and missing services in standalone-xts and standalone-rts profile > ----------------------------------------------------------------------------------------- > > Key: WFLY-8314 > URL: https://issues.jboss.org/browse/WFLY-8314 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged: > {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("host" => "default-host"), > ("setting" => "http-invoker") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"] > } > 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker] > 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server > 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand) > {code} > This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1859) Investigate and fix JDK9 modular params propagation to forked processes

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1859?page=com.atlassian.jira.plugi... ] Tomaz Cerar resolved WFCORE-1859. --------------------------------- Assignee: Tomaz Cerar (was: Richard Opalka) Resolution: Done solved by using diffrent style parameters without spaces. for example {noformat} --add-exports java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED {noformat} becomes: {noformat} --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED {noformat} JDK supports both. > Investigate and fix JDK9 modular params propagation to forked processes > ----------------------------------------------------------------------- > > Key: WFCORE-1859 > URL: https://issues.jboss.org/browse/WFCORE-1859 > Project: WildFly Core > Issue Type: Sub-task > Components: Server, Test Suite > Reporter: Richard Opalka > Assignee: Tomaz Cerar > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2363) Improve capability registration API

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-2363: ----------------------------------- Summary: Improve capability registration API Key: WFCORE-2363 URL: https://issues.jboss.org/browse/WFCORE-2363 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar we should be able to do things like {code:java} context.getServiceTarget().addCapability(IO_WORKER_RUNTIME_CAPABILITY, workerService) .setInitialMode(ServiceController.Mode.ON_DEMAND) .install(); {code} instead of longer version with figuring out service name etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7371) JAXRS endpoint - CDI injection to constructor doesn't work

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/WFLY-7371?page=com.atlassian.jira.plugin.... ] Ron Sigal commented on WFLY-7371: --------------------------------- RESTEASY-1538 is closed. > JAXRS endpoint - CDI injection to constructor doesn't work > ---------------------------------------------------------- > > Key: WFLY-7371 > URL: https://issues.jboss.org/browse/WFLY-7371 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 10.1.0.Final > Reporter: Tomas Remes > Assignee: Ron Sigal > > Deploying app with following JAXRS endpoint > {code} > @Path("/test") > public class MyTimeResource { > private final LocalDateTime dateTime; > @Inject > public MyTimeResource(LocalDateTime dateTime){ > this.dateTime = dateTime; > }; > } > {code} > is failing with following stack trace: > {noformat} > Caused by: java.lang.RuntimeException: RESTEASY003190: Could not find constructor for class: org.example.microprofile.MyTimeResource > at org.jboss.resteasy.spi.metadata.ResourceBuilder.constructor(ResourceBuilder.java:692) > at org.jboss.resteasy.plugins.server.resourcefactory.POJOResourceFactory.registered(POJOResourceFactory.java:42) > at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:208) > at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:194) > at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:180) > at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:157) > at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:76) > at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:409) > at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:250) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) > at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) > at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78) > at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) > at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250) > at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133) > at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546) > at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) > ... 6 more > {noformat} > Note that app contains beans.xml so the JAXRS resource should be really managed by CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017