May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1130) Elytron Client configuration file requires alias for keystore

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1130?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1130: ---------------------------------- The keystore-backed realm is also able to find a certificate by principal. We could possibly utilize similar logic to select a certificate by principal when an authentication principal is given. > Elytron Client configuration file requires alias for keystore > ------------------------------------------------------------- > > Key: ELY-1130 > URL: https://issues.jboss.org/browse/ELY-1130 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta38 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In Elytron Client configuration file all elements related to keystore (key-store-ssl-certificate, key-store-reference and key-store-credential) require element alias. It is difference from Elytron subsystem where alias is not required. > Usage of alias should be consistent between subsystem and Elytron Client configuration file. Elytron is able to found out certificate without passed alias if keystore includes just one entry. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8694) Upgrade HAL to 2.9.8.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-8694?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-8694: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/9950) > Upgrade HAL to 2.9.8.Final > -------------------------- > > Key: WFLY-8694 > URL: https://issues.jboss.org/browse/WFLY-8694 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8694) Upgrade HAL to 2.9.8.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-8694: --------------------------------- Summary: Upgrade HAL to 2.9.8.Final Key: WFLY-8694 URL: https://issues.jboss.org/browse/WFLY-8694 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8693) @Resource not working on Dynamic Servlets

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-8693?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-8693: ------------------------------------ Moved from WildFly Swarm. It seems that dynamic servlet registrations are not treated as regular EE components, ie. resource injection is not performed. > @Resource not working on Dynamic Servlets > ----------------------------------------- > > Key: WFLY-8693 > URL: https://issues.jboss.org/browse/WFLY-8693 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Dan Siviter > > When a dynamic servlet is used then {{@Resource}} does not work. When using {{@WebServlet}} it does inject fine and only appears to be associated with dynamic ones. Test used {{ManagedExecutorService}} but it may apply to more. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8693) @Resource not working on Dynamic Servlets

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-8693?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-8693: ------------------------------- Component/s: Web (Undertow) > @Resource not working on Dynamic Servlets > ----------------------------------------- > > Key: WFLY-8693 > URL: https://issues.jboss.org/browse/WFLY-8693 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Dan Siviter > > When a dynamic servlet is used then {{@Resource}} does not work. When using {{@WebServlet}} it does inject fine and only appears to be associated with dynamic ones. Test used {{ManagedExecutorService}} but it may apply to more. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1130) Elytron Client configuration file requires alias for keystore

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1130: --------------------------------- Summary: Elytron Client configuration file requires alias for keystore Key: ELY-1130 URL: https://issues.jboss.org/browse/ELY-1130 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse In Elytron Client configuration file all elements related to keystore (key-store-ssl-certificate, key-store-reference and key-store-credential) require element alias. It is difference from Elytron subsystem where alias is not required. Usage of alias should be consistent between subsystem and Elytron Client configuration file. Elytron is able to found out certificate without passed alias if keystore includes just one entry. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1130) Elytron Client configuration file requires alias for keystore

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1130?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1130: ------------------------------ Affects Version/s: 1.1.0.Beta38 > Elytron Client configuration file requires alias for keystore > ------------------------------------------------------------- > > Key: ELY-1130 > URL: https://issues.jboss.org/browse/ELY-1130 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta38 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In Elytron Client configuration file all elements related to keystore (key-store-ssl-certificate, key-store-reference and key-store-credential) require element alias. It is difference from Elytron subsystem where alias is not required. > Usage of alias should be consistent between subsystem and Elytron Client configuration file. Elytron is able to found out certificate without passed alias if keystore includes just one entry. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1130) Elytron Client configuration file requires alias for keystore

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1130?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1130: ------------------------------ Component/s: Authentication Client > Elytron Client configuration file requires alias for keystore > ------------------------------------------------------------- > > Key: ELY-1130 > URL: https://issues.jboss.org/browse/ELY-1130 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta38 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In Elytron Client configuration file all elements related to keystore (key-store-ssl-certificate, key-store-reference and key-store-credential) require element alias. It is difference from Elytron subsystem where alias is not required. > Usage of alias should be consistent between subsystem and Elytron Client configuration file. Elytron is able to found out certificate without passed alias if keystore includes just one entry. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8693) @Resource not working on Dynamic Servlets

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-8693?page=com.atlassian.jira.plugin.... ] Martin Kouba moved SWARM-1083 to WFLY-8693: ------------------------------------------- Project: WildFly (was: WildFly Swarm) Key: WFLY-8693 (was: SWARM-1083) Workflow: GIT Pull Request workflow (was: GIT Pull Request workflow with automatic PR triggers) Affects Version/s: 10.1.0.Final (was: 2017.2.0) (was: 2017.5.0) > @Resource not working on Dynamic Servlets > ----------------------------------------- > > Key: WFLY-8693 > URL: https://issues.jboss.org/browse/WFLY-8693 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Reporter: Dan Siviter > > When a dynamic servlet is used then {{@Resource}} does not work. When using {{@WebServlet}} it does inject fine and only appears to be associated with dynamic ones. Test used {{ManagedExecutorService}} but it may apply to more. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2757) DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2757?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFCORE-2757: ----------------------------------- Workaround Description: Require bean descriptor in weld subsystem: {{/subsystem=weld:write-attribute(name=require-bean-descriptor,value=true)}} was: Require bean descriptor in weld subsystem: {{/subsystem=weld:write-attribute(name=require-bean-descriptor,value=true}} > DUP leaks on undeploy causing WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default > --------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2757 > URL: https://issues.jboss.org/browse/WFCORE-2757 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 3.0.0.Beta17 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {noformat} > 20:11:08,590 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service > 20:11:08,594 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service > 20:11:08,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2) ISPN000094: Received new cluster view for channel server: [node1|4] (1) [node1] > ... > 20:11:08,794 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started clusterbench-ee7-singleton-jbossall.ear/clusterbench-ee7-ejb.jar cache from ejb container > 20:11:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Validator with qualifiers @Default > at injection point [UnbackedAnnotatedField] @Inject private org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator > at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validator(ValidationInterceptor.java:0) > at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362) > at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284) > at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:539) > at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:78) > at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:76) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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 May 2017