January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4287) CLI should show not show default value once value one of "alternatives" attributes was set

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4287?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-4287: ---------------------------------------- Assignee: (was: Brian Stansberry) > CLI should show not show default value once value one of "alternatives" attributes was set > ------------------------------------------------------------------------------------------ > > Key: WFCORE-4287 > URL: https://issues.jboss.org/browse/WFCORE-4287 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Miroslav Novak > Priority: Major > > If there are attributes which are "alternatives" and both of them are undefined then default value of one of the attributes is shown in CLI, for example: > {code} > [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default > elytron-domain=undefined > security-domain=other > {code} > at this moment when I try set elytron-domain: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:write-attribute(name=elytron-domain,value=ApplicationRealm) > {code} > then it shows: > {code} > [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default > elytron-domain=ApplicationDomain > security-domain=other > {code} > Can this be changed that it would show {{security-domain=undefined}} so it would not show default values anymore? Current display is confusing as it's not clear what is used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1748) Add support for a BiFunction<T, U, V> to TokenSecurityRealm.Builder for the principalClaimName

by Scott Stark (Jira)

[ https://issues.jboss.org/browse/ELY-1748?page=com.atlassian.jira.plugin.s... ] Scott Stark commented on ELY-1748: ---------------------------------- I ended up just adding an overloaded principalClaimNameI(Funtion<Attributes,String> func) method to the TokenSecurityRealm.Builder. The usage is illustrated in the org.wildfly.security.auth.realm.token.JwtSecurityRealmTest#{testAltPrincipaNames,testAltPrincipaNamesSubFallback} methods. > Add support for a BiFunction<T,U,V> to TokenSecurityRealm.Builder for the principalClaimName > -------------------------------------------------------------------------------------------- > > Key: ELY-1748 > URL: https://issues.jboss.org/browse/ELY-1748 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Affects Versions: 1.7.0.Final > Reporter: Scott Stark > Assignee: Scott Stark > Priority: Major > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I'm looking at using ELY to replace some of the custom auth code we have for the MP-JWT implementation in thorntail and elsewhere. While looking at using the org.wildfly.security.auth.realm.token.TokenSecurityRealm, I see that the claim used to extract the principal name from the token is a fixed claim name. In the MP-JWT spec we allow for a series of claims to be checked in a given order to attempt to obtain the principal name. What is needed is a BiFunction<BearerTokenEvidence,Attributes,String> or perhaps just a Funtion<Attributes,String> principalClaimNameFunction() method on the Builder to externalize the claim to principal name mapping. > I'll look at creating a pull request for this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11645) A way to prevent automatic changes of affinity when invoking clustered beans

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11645?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11645: ------------------------------------ Issue Type: Feature Request (was: Enhancement) Actually this is not an Enhancement, it is a Feature Request, as it involves a new form of user control of behavior. > A way to prevent automatic changes of affinity when invoking clustered beans > ---------------------------------------------------------------------------- > > Key: WFLY-11645 > URL: https://issues.jboss.org/browse/WFLY-11645 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, EJB > Reporter: Jan Martiska > Priority: Major > > When invoking a clustered bean, a user might want to set an affinity so that the invocations go to a particular node. This is done via EJB client APIs: > {noformat} > EJBClient.setStrongAffinity(beanProxy, new NodeAffinity("node1")); > {noformat} > however, if the bean is clustered, after each invocation, the affinity is automatically reset to a ClusterAffinity. So the user would have to apply this again before each invocation. There should be a way to tell EJB client to not do this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11645) A way to prevent automatic changes of affinity when invoking clustered beans

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11645?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11645: --------------------------------------- Assignee: (was: Jason Greene) > A way to prevent automatic changes of affinity when invoking clustered beans > ---------------------------------------------------------------------------- > > Key: WFLY-11645 > URL: https://issues.jboss.org/browse/WFLY-11645 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, EJB > Reporter: Jan Martiska > Priority: Major > > When invoking a clustered bean, a user might want to set an affinity so that the invocations go to a particular node. This is done via EJB client APIs: > {noformat} > EJBClient.setStrongAffinity(beanProxy, new NodeAffinity("node1")); > {noformat} > however, if the bean is clustered, after each invocation, the affinity is automatically reset to a ClusterAffinity. So the user would have to apply this again before each invocation. There should be a way to tell EJB client to not do this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11645) A way to prevent automatic changes of affinity when invoking clustered beans

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11645?page=com.atlassian.jira.plugin... ] Brian Stansberry moved JBEAP-13233 to WFLY-11645: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11645 (was: JBEAP-13233) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering EJB (was: Clustering) (was: EJB) Target Release: (was: 7.1.0.GA) Affects Version/s: (was: 7.1.0.CR2) > A way to prevent automatic changes of affinity when invoking clustered beans > ---------------------------------------------------------------------------- > > Key: WFLY-11645 > URL: https://issues.jboss.org/browse/WFLY-11645 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, EJB > Reporter: Jan Martiska > Assignee: Jason Greene > Priority: Major > > When invoking a clustered bean, a user might want to set an affinity so that the invocations go to a particular node. This is done via EJB client APIs: > {noformat} > EJBClient.setStrongAffinity(beanProxy, new NodeAffinity("node1")); > {noformat} > however, if the bean is clustered, after each invocation, the affinity is automatically reset to a ClusterAffinity. So the user would have to apply this again before each invocation. There should be a way to tell EJB client to not do this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1748) Add support for a BiFunction<T, U, V> to TokenSecurityRealm.Builder for the principalClaimName

by Scott Stark (Jira)

Scott Stark created ELY-1748: -------------------------------- Summary: Add support for a BiFunction<T,U,V> to TokenSecurityRealm.Builder for the principalClaimName Key: ELY-1748 URL: https://issues.jboss.org/browse/ELY-1748 Project: WildFly Elytron Issue Type: Task Components: Realms Affects Versions: 1.7.0.Final Reporter: Scott Stark Assignee: Scott Stark I'm looking at using ELY to replace some of the custom auth code we have for the MP-JWT implementation in thorntail and elsewhere. While looking at using the org.wildfly.security.auth.realm.token.TokenSecurityRealm, I see that the claim used to extract the principal name from the token is a fixed claim name. In the MP-JWT spec we allow for a series of claims to be checked in a given order to attempt to obtain the principal name. What is needed is a BiFunction<BearerTokenEvidence,Attributes,String> or perhaps just a Funtion<Attributes,String> principalClaimNameFunction() method on the Builder to externalize the claim to principal name mapping. I'll look at creating a pull request for this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11571) Upgrade FasterXML Jackson from 2.9.5 to 2.9.8

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11571?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11571: ------------------------------------ Fix Version/s: 15.x.x TBD > Upgrade FasterXML Jackson from 2.9.5 to 2.9.8 > --------------------------------------------- > > Key: WFLY-11571 > URL: https://issues.jboss.org/browse/WFLY-11571 > Project: WildFly > Issue Type: Component Upgrade > Components: XML Frameworks > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Priority: Major > Labels: downstream_dependency > Fix For: 16.0.0.Beta1, 15.x.x TBD > > > Tag: > https://github.com/FasterXML/jackson-core/releases/tag/jackson-core-2.9.8 > https://github.com/FasterXML/jackson-annotations/releases/tag/jackson-ann... > https://github.com/FasterXML/jackson-databind/releases/tag/jackson-databi... > https://github.com/FasterXML/jackson-modules-java8/releases/tag/jackson-m... > https://github.com/FasterXML/jackson-jaxrs-providers/releases/tag/jackson... > https://github.com/FasterXML/jackson-modules-base/releases/tag/jackson-mo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3477) MVEL: expression (1 + 2 * 3 + 4 * $v ) causes "no such method or function " for bind variable

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3477?page=com.atlassian.jira.plugi... ] Mario Fusco reopened DROOLS-3477: --------------------------------- > MVEL: expression (1 + 2 * 3 + 4 * $v ) causes "no such method or function " for bind variable > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-3477 > URL: https://issues.jboss.org/browse/DROOLS-3477 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.11.0.Final > Environment: MVEL2 2.4.2 Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Attachments: mvel2-var-test2.zip, mvel2-var-test3.zip > > > Similar issue was reported and fixed in DROOLS-2854, there is another pattern which does not work. > When MVEL evaluates > m.setStatus( 1 + 2 * 3 + 4 * m.getStatus() ); > the following exception happens. > {noformat} > Exception executing consequence for rule "Hello World" in com.sample: [Error: no such method or function: m] > [Near : {... m.setStatus( 1 + 2 * 3 + 4 * m.getStatus() ); ....}] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9977) Redundant CONSOLE log handler adding in CLI scripts for messaging-clustering* QS

by Sande Gilda (Jira)

[ https://issues.jboss.org/browse/WFLY-9977?page=com.atlassian.jira.plugin.... ] Sande Gilda reassigned WFLY-9977: --------------------------------- Assignee: Sande Gilda > Redundant CONSOLE log handler adding in CLI scripts for messaging-clustering* QS > -------------------------------------------------------------------------------- > > Key: WFLY-9977 > URL: https://issues.jboss.org/browse/WFLY-9977 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 12.0.0.Final > Reporter: Nikoleta Žiaková > Assignee: Sande Gilda > Priority: Major > > CLI scripts in messaging-clustering and messaging-clustering-singleton QS contain redundant step for adding CONSOLE log handler. They fails with: > {code} > Failure: WFLYCTL0212: Duplicate resource > {code} > The reason is that CONSOLE log handler is enabled by default. > Readme files mention adding the handler, too: > https://github.com/wildfly/quickstart/tree/master/messaging-clustering > https://github.com/wildfly/quickstart/tree/master/messaging-clustering-si... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11643) Update helloworld-mdb quickstarts expected console output in Readme

by Sande Gilda (Jira)

[ https://issues.jboss.org/browse/WFLY-11643?page=com.atlassian.jira.plugin... ] Sande Gilda reassigned WFLY-11643: ---------------------------------- Assignee: Sande Gilda (was: Eduardo Martins) > Update helloworld-mdb quickstarts expected console output in Readme > ------------------------------------------------------------------- > > Key: WFLY-11643 > URL: https://issues.jboss.org/browse/WFLY-11643 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Sande Gilda > Priority: Major > > As it is written in helloworld-mdb and helloworld-mdb-propertysubstitution Readme, the following line is expected to appear in console output: > {noformat} > INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221003: trying to deploy queue jms.queue.HelloWorldMDBQueue > {noformat} > But in 7.3.0.CD15 build (and older builds) this kind of info message is not shown anymore whereas helloworld quickstarts functionality is not influenced at all - see more details at [logs|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-q...]. > I suggest updating the mentioned Readmes in case you don't have an another resolution. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 January 2019