April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8551) Establish proper capability contract for mod_cluster undertow adapter

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8551?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8551: ---------------------------------------- This is an interesting -- kind of ;) -- design question. What's "mod_cluster" and what's "undertow"? I think the undertow adapter is really part of undertow, so it needs a capability from mod_cluster. The adapter code is in the mod_cluster source tree, which obscures this a bit, making the adapter seem more like a part of mod_cluster than would be the case if the code were moved to the "undertow" tree. (I'm not at all saying to move it.) Also, the adapter implements some interfaces from mod_cluster, which isn't a clear fit with capabilities. (I'm not at all saying that's wrong though.) Those interfaces are kind of like a custom integration API that a capability can expose to dependents, but the way they work is different. The required cap (mod_cluster) requires the dependent (adapter) to do something (expose interfaces via ServiceLoader) vs the custom runtime API approach where the required cap exposes something and the dependent looks that up and invokes on it. > Establish proper capability contract for mod_cluster undertow adapter > --------------------------------------------------------------------- > > Key: WFLY-8551 > URL: https://issues.jboss.org/browse/WFLY-8551 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > This was never exposed as there wasn't an expectation that somebody would depend on this. Initial contract + workaround introduced by https://github.com/wildfly/wildfly/pull/9897 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1007) Exception in authenticate() method of SecurityContextImpl is hidden

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1007?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1007. ----------------------------------- Resolution: Migrated to another ITS https://github.com/wildfly-security/elytron-web/issues/92 > Exception in authenticate() method of SecurityContextImpl is hidden > ------------------------------------------------------------------- > > Key: ELY-1007 > URL: https://issues.jboss.org/browse/ELY-1007 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > In case when {{authenticator.authenticate()}} in {{authenticate()}} method of {{org.wildfly.elytron.web.undertow.server.SecurityContextImpl}} [1] throws exception, then this exception is hidden and only internal server error status is returned. Thrown exception should be logged. > This issue can be cause of JBEAP-9377. > [1] https://github.com/wildfly-security/elytron-web/blob/49241df4afcc37158c54... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-64) [QE] - JMAN4-126 - Enable and Disable deployments in an Server Group

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-64?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-64: ------------------------------------- Labels: 5.0 (was: ) > [QE] - JMAN4-126 - Enable and Disable deployments in an Server Group > -------------------------------------------------------------------- > > Key: HAWKULARQE-64 > URL: https://issues.jboss.org/browse/HAWKULARQE-64 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Labels: 5.0 > > See [JMAN4-126|https://issues.jboss.org/browse/JMAN4-126] > Dev task for it [HAWKULAR-1165|https://issues.jboss.org/browse/HAWKULAR-1165] > This is 5.0 release planed feature, but is in development of 4.5. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-14) [QE] - JMAN4-117 - Specify the middleware metrics to collect

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-14?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-14: ------------------------------------- Labels: 5.0 mm-integration-hawkular-qe (was: mm-integration-hawkular-qe) > [QE] - JMAN4-117 - Specify the middleware metrics to collect > ------------------------------------------------------------ > > Key: HAWKULARQE-14 > URL: https://issues.jboss.org/browse/HAWKULARQE-14 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Priority: Minor > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-117|https://issues.jboss.org/browse/JMAN4-117] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8551) Establish proper capability contract for mod_cluster undertow adapter

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-8551: ------------------------------------ Summary: Establish proper capability contract for mod_cluster undertow adapter Key: WFLY-8551 URL: https://issues.jboss.org/browse/WFLY-8551 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 11.0.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar This was never exposed as there wasn't an expectation that somebody would depend on this. Initial contract + workaround introduced by https://github.com/wildfly/wildfly/pull/9897 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2653) Elytron, *-authentication-factory protocol attribute should be case insensitive

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2653?page=com.atlassian.jira.plugi... ] Jan Kalina moved WFLY-8471 to WFCORE-2653: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2653 (was: WFLY-8471) Component/s: Security (was: Security) > Elytron, *-authentication-factory protocol attribute should be case insensitive > ------------------------------------------------------------------------------- > > Key: WFCORE-2653 > URL: https://issues.jboss.org/browse/WFCORE-2653 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > > When I use "HTTP" in protocol attribute instead of "http", I get 403 instead of succesfull access. > According to http://www.rfc-base.org/txt/rfc-1738.txt > Scheme names consist of a sequence of characters. The lower case > letters "a"--"z", digits, and the characters plus ("+"), period > ("."), and hyphen ("-") are allowed. For resiliency, programs > interpreting URLs should treat upper case letters as equivalent to > lower case in scheme names (e.g., allow "HTTP" as well as "http"). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8471) Elytron, *-authentication-factory protocol attribute should be case insensitive

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8471?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-8471: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Elytron, *-authentication-factory protocol attribute should be case insensitive > ------------------------------------------------------------------------------- > > Key: WFLY-8471 > URL: https://issues.jboss.org/browse/WFLY-8471 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > > When I use "HTTP" in protocol attribute instead of "http", I get 403 instead of succesfull access. > According to http://www.rfc-base.org/txt/rfc-1738.txt > Scheme names consist of a sequence of characters. The lower case > letters "a"--"z", digits, and the characters plus ("+"), period > ("."), and hyphen ("-") are allowed. For resiliency, programs > interpreting URLs should treat upper case letters as equivalent to > lower case in scheme names (e.g., allow "HTTP" as well as "http"). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1070) Elytron, WWW-Authenticate Negotiate header is send although SPNEGO is misconfigured

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1070?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1070: ---------------------------------- Fix Version/s: 1.1.0.Beta36 > Elytron, WWW-Authenticate Negotiate header is send although SPNEGO is misconfigured > ----------------------------------------------------------------------------------- > > Key: ELY-1070 > URL: https://issues.jboss.org/browse/ELY-1070 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Labels: kerberos > Fix For: 1.1.0.Beta36 > > Attachments: kerberos_http_interface.pcap > > > If SPNEGO is misconfigured Negotiate header is still send back to client, although SPNEGO can't be used. > {code} > 13:19:20,861 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='BASIC' host-name='localhost.localdomain' protocol='http' > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) Handling AvailableRealmsCallback: realms = [fileSystemFallbackRealm] > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='CLIENT_CERT' host-name='localhost.localdomain' protocol='http' > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='CLIENT_CERT', hostName='localhost.localdomain', protocol='http'. > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='DIGEST' host-name='localhost.localdomain' protocol='http' > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='DIGEST', hostName='localhost.localdomain', protocol='http'. > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='FORM' host-name='localhost.localdomain' protocol='http' > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='FORM', hostName='localhost.localdomain', protocol='http'. > 13:19:20,862 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='SPNEGO' host-name='localhost.localdomain' protocol='http' > 13:19:20,863 TRACE [org.wildfly.security] (management task-6) Evaluating SPNEGO request: cached GSSContext = null > 13:19:20,863 TRACE [org.wildfly.security] (management task-6) Obtaining GSSCredential for the service from callback handler... > 13:19:20,863 TRACE [org.wildfly.security] (management task-6) No valid cached credential, obtaining new one... > 13:19:20,863 TRACE [org.wildfly.security] (management task-6) Logging in using LoginContext and subject [Subject: > ] > 13:19:20,863 INFO [stdout] (management task-6) Debug is true storeKey true useTicketCache false useKeyTab true doNotPrompt false ticketCache is null isInitiator false KeyTab is /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.4985635734744374940.keytab refreshKrb5Config is false principal is HTTP/wronghost(a)JBOSS.ORG tryFirstPass is false useFirstPass is false storePass is false clearPass is false > 13:19:20,863 INFO [stdout] (management task-6) principal is HTTP/wronghost(a)JBOSS.ORG > 13:19:20,863 INFO [stdout] (management task-6) Will use keytab > 13:19:20,863 INFO [stdout] (management task-6) Commit Succeeded > 13:19:20,863 INFO [stdout] (management task-6) > 13:19:20,863 TRACE [org.wildfly.security] (management task-6) Logging in using LoginContext and subject [Subject: > Principal: HTTP/wronghost(a)JBOSS.ORG > Private Credential: /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.4985635734744374940.keytab for HTTP/wronghost(a)JBOSS.ORG > ] succeed > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Creating GSSName for Principal 'HTTP/wronghost(a)JBOSS.ORG' > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Obtained GSSCredentialCredential [org.wildfly.security.credential.GSSKerberosCredential@1f] > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Handling ServerCredentialCallback: successfully obtained credential type type=class org.wildfly.security.credential.GSSKerberosCredential, algorithm=null, params=null > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Using SpnegoAuthenticationMechanism to authenticate HTTP/wronghost(a)JBOSS.ORG using the following mechanisms: [[Lorg.ietf.jgss.Oid;@4133c756] > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Caching GSSContext sun.security.jgss.GSSContextImpl@3adbbdae > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Caching KerberosTicket null > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Sent HTTP authorizations: [null] > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Request lacks valid authentication credentials > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) Handling MechanismInformationCallback type='HTTP' name='BEARER_TOKEN' host-name='localhost.localdomain' protocol='http' > 13:19:20,864 TRACE [org.wildfly.security] (management task-6) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='BEARER_TOKEN', hostName='localhost.localdomain', protocol='http'. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2387) CDI injection in entity listeners failing

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2387?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-2387: ------------------------------------ I pushed the updated unit test change to [https://github.com/scottmarlow/wildfly/tree/CDI_EAR] that seems to reproduce the same failure. Now, I am wondering what I forgot to do in the failing test case that causes the CDI extension to not be invoked (which is what I noticed from my debugging). I'll look a bit deeper. > CDI injection in entity listeners failing > ----------------------------------------- > > Key: WFLY-2387 > URL: https://issues.jboss.org/browse/WFLY-2387 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Class Loading, JPA / Hibernate > Affects Versions: 8.0.0.Beta1 > Reporter: Emond Papegaaij > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > Attachments: TEST-org.jboss.as.test.integration.ee.injection.support.jpa.EntityListenerInjectionSupportTestCase.xml > > > When trying to use CDI injection in JPA entity listeners, deployment fails with the following exception: > {code} > 16:16:37,448 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 15) MSC000001: Failed to start service jboss.persistenceunit."inject-ear.ear#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."inject-ear.ear#primary": java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:169) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25] > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463) [wildfly-security-manager-1.0.0.Beta3.jar:1.0.0.Beta3] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:178) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:128) > at org.jboss.weld.Container.instance(Container.java:65) > at org.jboss.weld.manager.BeanManagerImpl.getBeans(BeanManagerImpl.java:563) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:90) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:82) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:71) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory.buildListener(BeanManagerListenerFactory.java:57) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.resolveCallbacks(LegacyCallbackProcessor.java:168) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.processCallbacksForEntity(LegacyCallbackProcessor.java:71) > at org.hibernate.jpa.event.spi.JpaIntegrator.integrate(JpaIntegrator.java:150) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1837) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:854) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:847) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:396) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:846) > at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:151) > ... 8 more > {code} > I've created a small showcase of the problem: https://github.com/papegaaij/listener-injection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1434) Subsystem tests should automaticly test subsystem templates

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1434?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1434: ------------------------------------------ AIUI we explicitly decided not to deal with this, since the templates themselves are not proper xml. > Subsystem tests should automaticly test subsystem templates > ----------------------------------------------------------- > > Key: WFCORE-1434 > URL: https://issues.jboss.org/browse/WFCORE-1434 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Test Suite > Reporter: Tomaz Cerar > > Subsystem tests should automatically tests subsystem templates for parsing/marshalling > to prevent issues like WFLY-6350 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017