March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-987) Confusion in method with(AuthenticationContext other) in AuthenticationContext

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-987?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-987: ----------------------------- Affects Version/s: 1.1.0.Beta28 > Confusion in method with(AuthenticationContext other) in AuthenticationContext > ------------------------------------------------------------------------------ > > Key: ELY-987 > URL: https://issues.jboss.org/browse/ELY-987 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta28 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > org.wildfly.security.auth.client.AuthenticationContext includes method {{AuthenticationContext with(AuthenticationContext other)}} which creates new AuthenticationContext which includes rules and configuration and SSL context of given AuthenticationContext other. > However, in case when {{with}} method is used with index and another AuthenticationContext, then it includes only rules and configuration (SSL context is not used). There is also method {{withSsl}} which includes rules and SSL context, but no configuration. > I see three problems here: > * there is different behavior between {{with(AuthenticationContext other)}} and {{with(int idx, AuthenticationContext other)}} - first includes also SSL context > * javadoc for with(AuthenticationContext other) does not describe that SSL context from given {{AuthenticationContext other}} is also used. > * there is not able to include both configuration and SSL context into any AuthenticationContext on some position based on index > I report this as critical because it is part of public API - it should stay backward compatible once it will be released. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1431) Make property reactivity active by default

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1431?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1431: ----------------------------------- Assignee: Mario Fusco (was: Matteo Mortari) > Make property reactivity active by default > ------------------------------------------ > > Key: DROOLS-1431 > URL: https://issues.jboss.org/browse/DROOLS-1431 > Project: Drools > Issue Type: Enhancement > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-987) Confusion in method with(AuthenticationContext other) in AuthenticationContext

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-987: -------------------------------- Summary: Confusion in method with(AuthenticationContext other) in AuthenticationContext Key: ELY-987 URL: https://issues.jboss.org/browse/ELY-987 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical org.wildfly.security.auth.client.AuthenticationContext includes method {{AuthenticationContext with(AuthenticationContext other)}} which creates new AuthenticationContext which includes rules and configuration and SSL context of given AuthenticationContext other. However, in case when {{with}} method is used with index and another AuthenticationContext, then it includes only rules and configuration (SSL context is not used). There is also method {{withSsl}} which includes rules and SSL context, but no configuration. I see three problems here: * there is different behavior between {{with(AuthenticationContext other)}} and {{with(int idx, AuthenticationContext other)}} - first includes also SSL context * javadoc for with(AuthenticationContext other) does not describe that SSL context from given {{AuthenticationContext other}} is also used. * there is not able to include both configuration and SSL context into any AuthenticationContext on some position based on index I report this as critical because it is part of public API - it should stay backward compatible once it will be released. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Anton Giertli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Anton Giertli updated DROOLS-1461: ---------------------------------- Description: This works just fine: {code:java} rule "checkFirstName" dialect "mvel" when Message( message in ( "anton","giertli") ) then System.out.println("LHS OK"); end {code} But rule like this, won't fire: {code:java} global java.util.List $myGlobal; rule "checkFirstName" dialect "mvel" when Message( message in ( $myGlobal) ) then System.out.println("LHS OK"); end {code} was: This works just fine: {code:java} rule "checkFirstName" dialect "mvel" when Message( message in ( "anton","giertli") ) then System.out.println("LHS OK"); end {code} But rule like this, won't fire: global java.util.List $myGlobal; {code:java} rule "checkFirstName" dialect "mvel" when Message( message in ( $myGlobal) ) then System.out.println("LHS OK"); end {code} > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > {code:java} > global java.util.List $myGlobal; > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Anton Giertli (JIRA)

Anton Giertli created DROOLS-1461: ------------------------------------- Summary: In operator doesn't work with variable Key: DROOLS-1461 URL: https://issues.jboss.org/browse/DROOLS-1461 Project: Drools Issue Type: Bug Reporter: Anton Giertli Assignee: Edson Tirelli Attachments: operators.zip This works just fine: {code:java} rule "checkFirstName" dialect "mvel" when Message( message in ( "anton","giertli") ) then System.out.println("LHS OK"); end {code} But rule like this, won't fire: global java.util.List $myGlobal; {code:java} rule "checkFirstName" dialect "mvel" when Message( message in ( $myGlobal) ) then System.out.println("LHS OK"); end {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1461: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > global java.util.List $myGlobal; > > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Anton Giertli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Anton Giertli updated DROOLS-1461: ---------------------------------- Attachment: operators.zip > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > global java.util.List $myGlobal; > > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1461: -------------------------------- Component/s: core engine > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > global java.util.List $myGlobal; > > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7983) Credential store file isn't created when we add there new entry in embed-server mode.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7983?page=com.atlassian.jira.plugin.... ] Hynek Švábek commented on WFLY-7983: ------------------------------------ The problem is gone in EAP7.1.0.DR12 and EAP7.1.0.DR13. > Credential store file isn't created when we add there new entry in embed-server mode. > ------------------------------------------------------------------------------------- > > Key: WFLY-7983 > URL: https://issues.jboss.org/browse/WFLY-7983 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > Credential store file isn't created when we add there new entry in embed-server mode. > * ./bin/jboss-cli.sh > * embed-server > * /subsystem=elytron/credential-store=store001:add(uri="cr-store://test/store001.jceks?create=true", credential-reference={clear-text=pass123}) > * /subsystem=elytron/credential-store=store001/alias=alias001:add(secret-value=secretValue) > store001.jceks file should be created in JBOSS_HOME directory, but it doesn't. > When I stop embedded server and start standalone server everything work fine. > * stop-embedded-server > * ./bin/standalone.sh > * connect > * /subsystem=elytron/credential-store=store001/alias=alias001:add(secret-value=secretValue) > store001.jceks file is correctly created in JBOSS_HOME directory. > *NOTE:* > When I copy there store001.jceks file to JBOSS_HOME directory with same password to access as expected then entry is added correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8238) Unable to undefine credential-reference

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-8238?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-8238: ------------------------------------ Except the failing tests, investigating. > Unable to undefine credential-reference > --------------------------------------- > > Key: WFLY-8238 > URL: https://issues.jboss.org/browse/WFLY-8238 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Reporter: Claudio Miranda > Assignee: Tomas Hofman > > A bridge is added and a credential-reference is set. > However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value. > Also neither credential-reference and password are required=true, so they may be undefined. > {code} > /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ) > /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1}) > /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference) > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."}, > "rolled-back" => true > } > {code} > The same problem, when user adds a bridge with a password and later wants to undefine it to add a credential-reference > {code} > /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1) > /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password) > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not define any alternative to this attribute."}, > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017