November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7451) Extra commas in descriptions of *-outbound-socket-binding CLI resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7451?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-7451: ---------------------------------------- This is a WFCORE issue. > Extra commas in descriptions of *-outbound-socket-binding CLI resources > ----------------------------------------------------------------------- > > Key: WFLY-7451 > URL: https://issues.jboss.org/browse/WFLY-7451 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Chao Wang > Priority: Trivial > Labels: user_experience > > There are extra commas in descriptions of children resources of _socket-binding-group_ CLI resource (_local-destination-outbound-socket-binding_ and _remote-destination-outbound-socket-binding_). > E.g., there is "Configuration information for a, local destination, outbound socket binding.", there should be "Configuration information for a local destination outbound socket binding." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7437) Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7437?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-7437 at 11/3/16 10:23 AM: ------------------------------------------------------------ otp-credential-mapper={} is equivalent to undefined otp-credential-mapper on ModelNode level, which is allowed - you can have an ldap-realm without OTP credentials. There is not inconsistency. (Maybe in console parsing?) was (Author: honza889): otp-credential-mapper={} is equivalent to undefined otp-credential-mapper, which is allowed - you can have an ldap-realm without OTP credentials. The only forbidden thing is to have defined OTP credential mapping without attributes required for it. This is not inconsistency. > Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm > ------------------------------------------------------------------------ > > Key: WFLY-7437 > URL: https://issues.jboss.org/browse/WFLY-7437 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Minor > Labels: user_experience > > Attribute {{identity-mapping.otp-credential-mapper}} from Elytron ldap-realm should include Object which should contain four required attributes - algorithm-from, hash-from, seed-from, sequence-from. All of these attributes are set as nillable=false. > However CLI allows to run command where otp-credential-mapper attribute is added without any attributes which is inconsistent with their nillable=false. See following command: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > {code} > Moreover, this command results to configuration xml without any otp-credential-mapper: > {code} > <ldap-realm name="ldap-realm" dir-context="ldap"> > <identity-mapping rdn-identifier="uid"/> > </ldap-realm> > {code} > In case when at least one of otp-credential-mapper required attribute is added, then CLI command correctly fails: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={algorithm-from=atr}}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: hash-from may not be null", > "rolled-back" => true > } > {code} > Suggestion: > Do not allow to add {{identity-mapping.otp-credential-mapper}} without required attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-717) Creating Credentail Store from scratch when keystore file exists is successful.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-717?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek reassigned ELY-717: -------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Creating Credentail Store from scratch when keystore file exists is successful. > ------------------------------------------------------------------------------- > > Key: ELY-717 > URL: https://issues.jboss.org/browse/ELY-717 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I want to create new Credential Store from scratch and keystore file exists is successful. > In my opinion right behaviour is failure. > For behaviour like this when multiple Credential Stores use one keystore file I don't need use parameter "create.storage=true". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-717) Creating Credentail Store from scratch when keystore file exists is successful.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-717?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-717: ----------------------------- Component/s: Credential Store > Creating Credentail Store from scratch when keystore file exists is successful. > ------------------------------------------------------------------------------- > > Key: ELY-717 > URL: https://issues.jboss.org/browse/ELY-717 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Peter Skopek > > When I want to create new Credential Store from scratch and keystore file exists is successful. > In my opinion right behaviour is failure. > For behaviour like this when multiple Credential Stores use one keystore file I don't need use parameter "create.storage=true". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7437) Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7437?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7437: ---------------------------------- otp-credential-mapper={} is equivalent to undefined otp-credential-mapper, which is allowed - you can have an ldap-realm without OTP credentials. The only forbidden thing is to have defined OTP credential mapping without attributes required for it. This is not inconsistency. > Inconsistencies in otp-credential-mapper attribute of Elytron ldap-realm > ------------------------------------------------------------------------ > > Key: WFLY-7437 > URL: https://issues.jboss.org/browse/WFLY-7437 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Minor > Labels: user_experience > > Attribute {{identity-mapping.otp-credential-mapper}} from Elytron ldap-realm should include Object which should contain four required attributes - algorithm-from, hash-from, seed-from, sequence-from. All of these attributes are set as nillable=false. > However CLI allows to run command where otp-credential-mapper attribute is added without any attributes which is inconsistent with their nillable=false. See following command: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > {code} > Moreover, this command results to configuration xml without any otp-credential-mapper: > {code} > <ldap-realm name="ldap-realm" dir-context="ldap"> > <identity-mapping rdn-identifier="uid"/> > </ldap-realm> > {code} > In case when at least one of otp-credential-mapper required attribute is added, then CLI command correctly fails: > {code} > /subsystem=elytron/ldap-realm=ldap-realm:add(dir-context=ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={algorithm-from=atr}}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0155: hash-from may not be null", > "rolled-back" => true > } > {code} > Suggestion: > Do not allow to add {{identity-mapping.otp-credential-mapper}} without required attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-717) Creating Credentail Store from scratch when keystore file exists is successful.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-717: -------------------------------- Summary: Creating Credentail Store from scratch when keystore file exists is successful. Key: ELY-717 URL: https://issues.jboss.org/browse/ELY-717 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse When I want to create new Credential Store from scratch and keystore file exists is successful. In my opinion right behaviour is failure. For behaviour like this when multiple Credential Stores use one keystore file I don't need use parameter "create.storage=true". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1677?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1677: ------------------------------------------ +1 to Kabir's suggestion, although I don't know if we need to do anything complicated about testing that they have a test. It's fine to do though if it's easy. The existing method can just be a protected util method that people can use in a test if they want to. As long as we do a one time confirmation that all the existing working tests still happen I think that's good enough. > 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.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6899) Upgrade RESTEasy to 3.1.0.CR3

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-6899?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-6899: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9330 (was: https://github.com/wildfly/wildfly/pull/9252) > Upgrade RESTEasy to 3.1.0.CR3 > ----------------------------- > > Key: WFLY-6899 > URL: https://issues.jboss.org/browse/WFLY-6899 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6899) Upgrade RESTEasy to 3.1.0.CR3

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-6899?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-6899: ---------------------------------- Summary: Upgrade RESTEasy to 3.1.0.CR3 (was: Upgrade RESTEasy to 3.1.0.CR2) > Upgrade RESTEasy to 3.1.0.CR3 > ----------------------------- > > Key: WFLY-6899 > URL: https://issues.jboss.org/browse/WFLY-6899 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-711) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-711?page=com.atlassian.jira.plugin.sy... ] Jan Kalina deleted ELY-711: --------------------------- > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-711 > URL: https://issues.jboss.org/browse/ELY-711 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Jan Kalina > > Basically Elytron clone of JBEAP-4114. > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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