November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1677) Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplates cope with substitutions properly

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1677?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-1677: ------------------------------------- Note that the testSchemaOfSubsystemTemplate test is opt-in. If you don't override org.jboss.as.subsystem.test.AbstractSubsystemBaseTest#getSubsystemTemplatePaths, this test will not be run. > Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplates cope with substitutions properly > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1677 > URL: https://issues.jboss.org/browse/WFCORE-1677 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 2.2.0.CR8 > Reporter: Radoslav Husar > Assignee: Kabir Khan > Priority: Minor > > It sounds to me that the test should really be validating the generated XML files, rather than the templates. > {noformat} > testSchemaOfSubsystemTemplates[8](org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase) Time elapsed: 0.052 sec <<< FAILURE! > java.lang.AssertionError: error: cvc-complex-type.2.4.b: The content of element 'subsystem' is not complete. One of '{"urn:jboss:domain:infinispan:4.0":cache-container}' is expected. > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.as.subsystem.test.SchemaValidator$1.error(SchemaValidator.java:73) > at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282) > at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:481) > at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3571) > at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(XMLSchemaValidator.java:3508) > at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(XMLSchemaValidator.java:3434) > at org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(XMLSchemaValidator.java:3336) > at org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(XMLSchemaValidator.java:2383) > at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:894) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:673) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1645) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324) > at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:875) > at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:798) > at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(StreamValidatorHelper.java:186) > at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:129) > at javax.xml.validation.Validator.validate(Validator.java:124) > at org.jboss.as.subsystem.test.SchemaValidator.validateXML(SchemaValidator.java:123) > at org.jboss.as.subsystem.test.SchemaValidator.validateXML(SchemaValidator.java:101) > at org.jboss.as.subsystem.test.AbstractSubsystemBaseTest.testSchemaOfSubsystemTemplates(AbstractSubsystemBaseTest.java:144) > at org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSchemaOfSubsystemTemplates(SubsystemParsingTestCase.java:130) > Results : > Failed tests: > SubsystemParsingTestCase.testSchemaOfSubsystemTemplates:130->AbstractSubsystemBaseTest.testSchemaOfSubsystemTemplates:144 error: cvc-complex-type.2.4.b: The content of element 'subsystem' is not complete. One of '{"urn:jboss:domain:infinispan:4.0":cache-container}' is expected. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-709) SPNEGO should allow to pass custom GSSManager

by Jan Kalina (JIRA)

Jan Kalina created ELY-709: ------------------------------ Summary: SPNEGO should allow to pass custom GSSManager Key: ELY-709 URL: https://issues.jboss.org/browse/ELY-709 Project: WildFly Elytron Issue Type: Feature Request Components: Authentication Mechanisms Reporter: Jan Kalina Assignee: Jan Kalina SPNEGO mechanism (and its factory) should accept a GSSManager parameter whose default value is GSSManager.getInstance(). See org.wildfly.security.sasl.gs2.Gs2SaslServerFactory for reference. https://github.com/wildfly-security/wildfly-elytron/pull/534#discussion_r... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-708?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-708: ----------------------------- Component/s: (was: Credential Store) > Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-708 > URL: https://issues.jboss.org/browse/ELY-708 > Project: WildFly Elytron > Issue Type: Bug > Components: KeyStores > Affects Versions: 1.1.0.Beta11 > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I create elytron key-store with wrong password and execute *store* operation > /subsystem=elytron/key-store=firefly:store() > then the key-store file is replace with zero size.file. > I can see this error message > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-708?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek reassigned ELY-708: -------------------------------- Assignee: Darran Lofthouse (was: Peter Skopek) > Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-708 > URL: https://issues.jboss.org/browse/ELY-708 > Project: WildFly Elytron > Issue Type: Bug > Components: KeyStores > Affects Versions: 1.1.0.Beta11 > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > When I create elytron key-store with wrong password and execute *store* operation > /subsystem=elytron/key-store=firefly:store() > then the key-store file is replace with zero size.file. > I can see this error message > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-708?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek reassigned ELY-708: -------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-708 > URL: https://issues.jboss.org/browse/ELY-708 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta11 > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I create elytron key-store with wrong password and execute *store* operation > /subsystem=elytron/key-store=firefly:store() > then the key-store file is replace with zero size.file. > I can see this error message > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-708?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-708: ----------------------------- Affects Version/s: 1.1.0.Beta11 > Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-708 > URL: https://issues.jboss.org/browse/ELY-708 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta11 > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I create elytron key-store with wrong password and execute *store* operation > /subsystem=elytron/key-store=firefly:store() > then the key-store file is replace with zero size.file. > I can see this error message > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-708?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-708: ----------------------------- Component/s: Credential Store KeyStores > Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. > -------------------------------------------------------------------------------------------------------------- > > Key: ELY-708 > URL: https://issues.jboss.org/browse/ELY-708 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store, KeyStores > Affects Versions: 1.1.0.Beta11 > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I create elytron key-store with wrong password and execute *store* operation > /subsystem=elytron/key-store=firefly:store() > then the key-store file is replace with zero size.file. > I can see this error message > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-708) Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-708: -------------------------------- Summary: Elytron key-store with WrongPassword is replace with zero size file when I process "store" operation over CLI. Key: ELY-708 URL: https://issues.jboss.org/browse/ELY-708 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse When I create elytron key-store with wrong password and execute *store* operation /subsystem=elytron/key-store=firefly:store() then the key-store file is replace with zero size.file. I can see this error message {code} { "outcome" => "failed", "result" => undefined, "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: password can't be null", "rolled-back" => true } {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1918) re-enable quote parsing

by Hisanobu Okuda (JIRA)

Hisanobu Okuda created WFCORE-1918: -------------------------------------- Summary: re-enable quote parsing Key: WFCORE-1918 URL: https://issues.jboss.org/browse/WFCORE-1918 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 3.0.0.Alpha11 Reporter: Hisanobu Okuda The fix for WFCORE-1804 was committed [here|https://github.com/wildfly/wildfly-core/commit/027bfe959988b25e45771...]. It has a side-effect that it disables quote parsing. Now the [another fix|https://github.com/aeshell/aesh/commit/0e8aa5cf514d5af81b16f7741c92a6...] which does not have the side-effect was committed in [aesh|https://github.com/aeshell/aesh]. The following line in the [previous fix|ttps://github.com/wildfly/wildfly-core/commit/027bfe959988b25e4577149...] should be removed, when the new aesh version is released (0.66.11 or 12?). ??cli/src/main/java/org/jboss/as/cli/impl/CommandContextImpl.java:495?? {code} settings.parsingQuotes(false); {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7442) Capability org.wildfly.undertow.listener needs a well defined contract

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7442?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7442: ------------------------------------ Assignee: Stuart Douglas (was: Ingo Weiss) > Capability org.wildfly.undertow.listener needs a well defined contract > ---------------------------------------------------------------------- > > Key: WFLY-7442 > URL: https://issues.jboss.org/browse/WFLY-7442 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 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 2016