April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13366) Update reference to wildfly-credential-reference_1_1.xsd for future agroal XSD

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13366?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13366: ------------------------------------ Priority: Blocker (was: Major) > Update reference to wildfly-credential-reference_1_1.xsd for future agroal XSD > ------------------------------------------------------------------------------ > > Key: WFLY-13366 > URL: https://issues.redhat.com/browse/WFLY-13366 > Project: WildFly > Issue Type: Sub-task > Components: Agroal > Reporter: Jeff Mesnil > Assignee: Brian Stansberry > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13363) Update reference to wildfly-credential-reference_1_1.xsd for future jgroups XSD

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13363?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13363: ------------------------------------ Priority: Blocker (was: Major) > Update reference to wildfly-credential-reference_1_1.xsd for future jgroups XSD > ------------------------------------------------------------------------------- > > Key: WFLY-13363 > URL: https://issues.redhat.com/browse/WFLY-13363 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13365) Update reference to wildfly-credential-reference_1_1.xsd for future resource-adapters XSD

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13365?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13365: ------------------------------------ Priority: Blocker (was: Major) > Update reference to wildfly-credential-reference_1_1.xsd for future resource-adapters XSD > ----------------------------------------------------------------------------------------- > > Key: WFLY-13365 > URL: https://issues.redhat.com/browse/WFLY-13365 > Project: WildFly > Issue Type: Sub-task > Components: JCA > Reporter: Jeff Mesnil > Assignee: Stefano Maestri > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13364) Update reference to wildfly-credential-reference_1_1.xsd for future datasources XSD

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13364?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13364: ------------------------------------ Priority: Blocker (was: Major) > Update reference to wildfly-credential-reference_1_1.xsd for future datasources XSD > ----------------------------------------------------------------------------------- > > Key: WFLY-13364 > URL: https://issues.redhat.com/browse/WFLY-13364 > Project: WildFly > Issue Type: Sub-task > Components: JCA > Reporter: Jeff Mesnil > Assignee: Stefano Maestri > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12510) Update usages of wildfly-credential-reference_1_0.xsd to the new wildfly-credential-reference_1_1.xsd for new schemas

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12510?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-12510: ------------------------------------ Priority: Blocker (was: Major) > Update usages of wildfly-credential-reference_1_0.xsd to the new wildfly-credential-reference_1_1.xsd for new schemas > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12510 > URL: https://issues.redhat.com/browse/WFLY-12510 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Farah Juma > Assignee: Jeff Mesnil > Priority: Blocker > > With WFCORE-4150, the WildFly Core's urn:jboss:domain:13.0 namespace now references wildfly-credential-reference_1_1.xsd. > WildFly full tests that any schemas that we shipped is up to date with the latest urn:jboss:domain:13.0 namespace in StandardConfigsXMLValidationUnitTestCase tests. > However when this test resolves urn:jboss:domain:13.0, it also resolve urn:wildfly:credential-reference:1.1 and then the test fails because subsystems schemas that references urn:wildfly:credential-reference:1.0 are incorrectly considered not updated. > Released schemas must not be updated with urn:wildfly:credential-reference:1.1 as they are already out in the open. > However every new schemas that will be released with WildFly 20 must ensure that they will updated their references from urn:wildfly:credential-reference:1.0 to urn:wildfly:credential-reference:1.1. > I'll create separate WFLY issues for each involved component as they may update their schemas at different time during the development of WildFly 20. > There is no need to update the schema just for this reference change but if the schema is updated for another reason, then the reference to urn:wildfly:credential-reference MUST be updated -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1313) User with slash or backslash char in LDAP name cannot log in through security-realm

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-1313?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-1313: ------------------------------------- Priority: Major (was: Minor) > User with slash or backslash char in LDAP name cannot log in through security-realm > ----------------------------------------------------------------------------------- > > Key: WFCORE-1313 > URL: https://issues.redhat.com/browse/WFCORE-1313 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency > Attachments: users.ldif > > > According to LDAP specification [1], DN can contain slash char without escaping or escaped backslash, etc. > I am not able to log in to management console with username "Slash/Char" or "Back\Slash". But I would be able to log in there. > I can see this in Wireshark > *Slash/Char* > {code} > LDAPMessage bindRequest(1) ""uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple > LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : "uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x22 0x75 0x69 0x64 0x3D 0x53 0x6C 0x61 0x73 0x68 0x2F 0x43 0x68 0x61 0x72 0x2 > {code} > You can see there quotation marks around *uid=Slash/Char*. > *Back\Slash* > {code} > LDAPMessage bindRequest(1) "uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple > LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x75 0x69 0x64 0x3D 0x42 0x61 0x63 0x6B 0x5C 0x5C 0x5C 0x53 0x6C 0x61 0x73 0x6 > {code} > You can see there three backslash chars. > In my opinion problem can be somewhere around this > {code} > javax.naming.NameImpl.stringifyComp(String comp) > {code} > [1] https://tools.ietf.org/html/rfc2253#section-3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.redhat.com/browse/WFLY-10554?page=com.atlassian.jira.plugi... ] Radoslav Ivanov edited comment on WFLY-10554 at 4/14/20 2:45 AM: ----------------------------------------------------------------- I understand it is a private module and it is not recommended to use it. However, there is a compile dependency (see my previous comments and snapshot image; also in maven central repo metrics is listed as a compile dependency of opensaml-core) and sometimes could be a matter of JVM classloading algorithm to hit class not found exception/class not def found error. It could be easily reproduced, also mentioned in previous comments, as follow (calling org.opensaml.core.config.InitializationService.initialize()): {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} was (Author: rady66): I understand it is a private module and it is not recommended to use it. However, there is a compile dependency (see my previous comments and snapshot image; also it listed in maven central repo that metrics is a compile dependency of opensaml-core) and sometimes could be a matter of JVM classloading algorithm to hit class not found exception/class not def found error. It could be easily reproduced, also mentioned in previous comments, as follow (calling org.opensaml.core.config.InitializationService.initialize()): {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.redhat.com/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Major > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.redhat.com/browse/WFLY-10554?page=com.atlassian.jira.plugi... ] Radoslav Ivanov commented on WFLY-10554: ---------------------------------------- I understand it is a private module and it is not recommended to use it. However, there is a compile dependency (see my previous comments and snapshot image; also it listed in maven central repo that metrics is a compile dependency of opensaml-core) and sometimes could be a matter of JVM classloading algorithm to hit class not found exception/class not def found error. It could be easily reproduced, also mentioned in previous comments, as follow (calling org.opensaml.core.config.InitializationService.initialize()): {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.redhat.com/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Major > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2467: -------------------------------- This picks up the default config: {{udp.xml}}. However, it can't be picked up from {{.conf}}, but needs to be found in {{./classes}} or from the JAR. > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Patrick Reinhart (Jira)

Patrick Reinhart created JGRP-2467: -------------------------------------- Summary: Constructing a JChannel using the default Constructor fails while parsing version '${version}' Key: JGRP-2467 URL: https://issues.redhat.com/browse/JGRP-2467 Project: JGroups Issue Type: Bug Affects Versions: 4.2.2 Reporter: Patrick Reinhart Assignee: Bela Ban Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} {code} java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) at org.jgroups.JChannel.<init>(JChannel.java:107) at org.jgroups.JChannel.<init>(JChannel.java:98) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 2020