November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1373) IBM JDK, SPNEGO + FORM; with invalid ticket 200 status code is returned

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1373?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1373: ---------------------------------- Fix Version/s: 1.1.12.CR1 > IBM JDK, SPNEGO + FORM; with invalid ticket 200 status code is returned > ----------------------------------------------------------------------- > > Key: ELY-1373 > URL: https://issues.jboss.org/browse/ELY-1373 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Beta3 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Major > Fix For: 1.1.12.CR1, 1.2.0.Beta9 > > > Given SPNEGO + FORM authentication configuration. And running on IBM java. > When invalid kerberos ticket is send > Then status code 200 is returned with http form. > While on Oracle JDK {{gssContext.isEstablished()}} returns true for invalid client ticket (negotiate with wrong domain JBOSS.COM), so SPNEGO mechanism sends bare challenge after failed authorization, on IBM JDK it returns false immediately, so mechanism fail without sending challenge - to be consistent should be send in both cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-396) Undertow HTTPS listener does not accept EXPORT40 and EXPORT56 cipher strings

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-396?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-396: --------------------------------- Fix Version/s: 1.1.12.CR1 > Undertow HTTPS listener does not accept EXPORT40 and EXPORT56 cipher strings > ---------------------------------------------------------------------------- > > Key: ELY-396 > URL: https://issues.jboss.org/browse/ELY-396 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.0.2.Final > Reporter: Ondrej Kotek > Assignee: Jan Kalina > Priority: Minor > Fix For: 1.1.12.CR1, 1.2.0.Beta3 > > > Undertow HTTPS listener does not accept EXPORT40 and EXPORT56 cipher strings in enabled-cipher-suites attribute. They are accepted in EAP 6.4. > According to OpenSSL documentation [1], and according to Elytron documentation [2], the cipher strings should be accepted. > [1] https://www.openssl.org/docs/man1.0.2/apps/ciphers.html > [2] http://wildfly-security.github.io/wildfly-elytron/org/wildfly/security/ss... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1704) Release WildFly Elytron 1.1.12.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1704?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1704. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.12.Final > ------------------------------------ > > Key: ELY-1704 > URL: https://issues.jboss.org/browse/ELY-1704 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.1.12.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-481) Update Kiali Test Mesh Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-481?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-481. ------------------------------------------- Resolution: Done > Update Kiali Test Mesh Job > -------------------------- > > Key: SWSQE-481 > URL: https://issues.jboss.org/browse/SWSQE-481 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Kiali Test Mesh Job needs to have the option to install istioctl -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11269) Clean up the jacorb subsystem dependency tree

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11269: --------------------------------------- Summary: Clean up the jacorb subsystem dependency tree Key: WFLY-11269 URL: https://issues.jboss.org/browse/WFLY-11269 Project: WildFly Issue Type: Sub-task Components: IIOP Reporter: Brian Stansberry Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11268) Eliminate ServiceBuilder's addDependencies() usages

by Richard Opalka (Jira)

Richard Opalka created WFLY-11268: ------------------------------------- Summary: Eliminate ServiceBuilder's addDependencies() usages Key: WFLY-11268 URL: https://issues.jboss.org/browse/WFLY-11268 Project: WildFly Issue Type: Sub-task Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 15.0.0.Alpha1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11259) Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

by Adam Bialas (Jira)

[ https://issues.jboss.org/browse/WFLY-11259?page=com.atlassian.jira.plugin... ] Adam Bialas updated WFLY-11259: ------------------------------- Description: I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory and the application fails to deploy. I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. I created jboss-deployment-structure: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <exclusions> <module name="org.dom4j"/> </exclusions> </deployment> </jboss-deployment-structure> Even though I get the same exception so I suppose both jars are loaded and cause problems. I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem. was: I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory and the application fails to deploy. I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. I created jboss-deployment-structure: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <exclusions> <module name="org.dom4j"/> </exclusions> </deployment> </jboss-deployment-structure> Even though I get the same exception so I suppose both jars are loaded and cause problems. > Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > ------------------------------------------------------------------------------------------ > > Key: WFLY-11259 > URL: https://issues.jboss.org/browse/WFLY-11259 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Final > Reporter: Adam Bialas > Assignee: Jason Greene > Priority: Major > > I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown: > org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > and the application fails to deploy. > I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used. > I created jboss-deployment-structure: > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <deployment> > <exclusions> > <module name="org.dom4j"/> > </exclusions> > </deployment> > </jboss-deployment-structure> > Even though I get the same exception so I suppose both jars are loaded and cause problems. > I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-424) Create Maistra Message Bus Consumer Job

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-424?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-424: ------------------------------------ Example producer job: http://pastebin.test.redhat.com/665492 > Create Maistra Message Bus Consumer Job > --------------------------------------- > > Key: SWSQE-424 > URL: https://issues.jboss.org/browse/SWSQE-424 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > This job will: > - Consume the Message Bus Maistra build notice > - Run the Maistra job (deploy Maistra, bookinfo, kiali) > - Traffic to bookinfo > - Run E2E tests -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4179) Refactor MBeanRegistrationService from WildFly-Core to WildFly

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4179?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4179: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3580 (was: https://github.com/wildfly/wildfly-core/pull/3568) > Refactor MBeanRegistrationService from WildFly-Core to WildFly > -------------------------------------------------------------- > > Key: WFCORE-4179 > URL: https://issues.jboss.org/browse/WFCORE-4179 > Project: WildFly Core > Issue Type: Sub-task > Components: JMX > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 7.0.0.Alpha5 > > > MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4179) Refactor MBeanRegistrationService from WildFly-Core to WildFly

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4179?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4179: ----------------------------------- Description: MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. (was: In order to be able to migrate SAR WildFly subsystem to new MSC API we need to enrich MBeanRegistrationService to support new MSC API.) > Refactor MBeanRegistrationService from WildFly-Core to WildFly > -------------------------------------------------------------- > > Key: WFCORE-4179 > URL: https://issues.jboss.org/browse/WFCORE-4179 > Project: WildFly Core > Issue Type: Sub-task > Components: JMX > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 7.0.0.Alpha5 > > > MBeanRegistrationService have been moved to WildFly so we can eliminate it from WildFly-Core JMX subsystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 November 2018