November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7598) can not configure Artemis's SQLProvider.Factory

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7598: --------------------------------- Summary: can not configure Artemis's SQLProvider.Factory Key: WFLY-7598 URL: https://issues.jboss.org/browse/WFLY-7598 Project: WildFly Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil The messaging-activemq integration code erroneously uses the GenericSQLProvider.Factory() implementation when Artemis server is started which overrides the factory that is configured with the journal-sql-provider-factory attribute. -- 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/15/16 9:21 AM: ------------------------------------------------------------ First problem is in using model.get(...) instead of DEFINITION.resolveModelAttribute(context, model) The second problem is in console parsing - in input of performRuntime of ADD operation: * add(users-properties={path=$SOME_PATH},groups-properties={}) gives groups-properties=OBJECT{} * add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) gives otp-credential-mapper=UNDEFINED -> the problem is in representation of {} in input of performRuntime. was (Author: honza889): Note: Problem is in using model.get(...) instead of DEFINITION.resolveModelAttribute(context, model) > 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] (WFCORE-1902) Error messages from CLI batch should be more informative

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ] Marek Kopecký commented on WFCORE-1902: --------------------------------------- [~jdenise]: Do you have some ETA for this? I plan to clone this enhancement to JBEAP project and set target releaseEAP 7.2.0. Do you agree? Or do you plan to implement this in EAP 7.1.0? > Error messages from CLI batch should be more informative > -------------------------------------------------------- > > Key: WFCORE-1902 > URL: https://issues.jboss.org/browse/WFCORE-1902 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Alpha10 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Labels: user_experience > > *Description of problem:* > Error messages from CLI batch should be more informative > *Steps to Reproduce:* > {noformat} > cat <<EOF >a > batch > :read-attribute(name=product-version) > :read-attribute(name=product-name) > :read-attribute(name=nonsence) > :read-attribute(name=product-name) > run-batch > EOF > ./jboss-cli.sh -c --file=a > {noformat} > *Actual results:* > {noformat} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}} > {noformat} > *Expected results:* > I can imagine content like following could be helpful for troubleshooting: > {noformat} > { > "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => { > "Operation step-3" => { > "operation" => ":read-attribute(name=nonsence)" > "response" => "WFLYCTL0201: Unknown attribute 'nonsence'" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7597) can not configure Artemis's SQLProvider.Factory

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7597: --------------------------------- Summary: can not configure Artemis's SQLProvider.Factory Key: WFLY-7597 URL: https://issues.jboss.org/browse/WFLY-7597 Project: WildFly Issue Type: Bug Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil The messaging-activemq integration code erroneously uses the GenericSQLProvider.Factory() implementation when Artemis server is started which overrides the factory that is configured with the journal-sql-provider-factory attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1991) Upgrade to JBoss Remoting 5.0.0.Beta8

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1991: ---------------------------------------- Summary: Upgrade to JBoss Remoting 5.0.0.Beta8 Key: WFCORE-1991 URL: https://issues.jboss.org/browse/WFCORE-1991 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha13 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1990) Upgrade to WildFly Elytron 1.1.0.Beta14

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1990: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta14 Key: WFCORE-1990 URL: https://issues.jboss.org/browse/WFCORE-1990 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha13 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1359) Race condition in MVELDialectRuntimeData.getParserConfiguration

by Anuj Shah (JIRA)

Anuj Shah created DROOLS-1359: --------------------------------- Summary: Race condition in MVELDialectRuntimeData.getParserConfiguration Key: DROOLS-1359 URL: https://issues.jboss.org/browse/DROOLS-1359 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final, 5.5.0.Final Reporter: Anuj Shah Assignee: Mario Fusco MVELDialectRuntimeData attempts to hold a lazy loaded ParserConfiguration. The getParserConfiguration method sets this to a new configuration object and then sets the imports on the configuration. Between these two steps another thread could retrieve the stale configuration and use it. This could result in a number of exceptions in compilation. A simple fix is to delay assignment of new ParserConfiguration until after the imports are set. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7596) Elytron missing constant-role-decoder

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7596?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-7309 to WFLY-7596: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7596 (was: JBEAP-7309) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR8) > Elytron missing constant-role-decoder > ------------------------------------- > > Key: WFLY-7596 > URL: https://issues.jboss.org/browse/WFLY-7596 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > > There is no {{constant-role-decoder}}, however all of other mappers have constant-* variant: > {code} > [standalone@localhost:9990 /] /subsystem=elytron/constant-<TAB> > constant-name-rewriter constant-permission-mapper constant-principal-decoder constant-realm-mapper constant-role-mapper > {code} > It can be useful for simple applications / demos / testing ... > Please add it for the sake of completeness. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-211) Client-side trust store configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-211?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-211: --------------------------------- Fix Version/s: 1.1.0.Beta15 (was: 1.1.0.Beta14) > Client-side trust store configuration > ------------------------------------- > > Key: ELY-211 > URL: https://issues.jboss.org/browse/ELY-211 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta15 > > > Lest I forget. The client needs the ability to supplement the default trust store, to restrict the set of acceptable peer certificates/signers, for mutual authentication purposes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-298: --------------------------------- Fix Version/s: 1.1.0.Beta15 (was: 1.1.0.Beta14) > load-from/uri keystore xsd/parser mismatch > ------------------------------------------ > > Key: ELY-298 > URL: https://issues.jboss.org/browse/ELY-298 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The xsd has > {code} > <xsd:complexType name="key-store-type"> > <xsd:sequence minOccurs="1" maxOccurs="1"> >  > <xsd:choice minOccurs="1" maxOccurs="1"> > <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/> > {code} > The parser seems to look for 'uri' rather than 'load-from' -- 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