November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2125) Lists as unary tests should be checked for containment, not equality

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2125?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2125: ---------------------------------- Sprint: 2017 Week 47-48 > Lists as unary tests should be checked for containment, not equality > -------------------------------------------------------------------- > > Key: DROOLS-2125 > URL: https://issues.jboss.org/browse/DROOLS-2125 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Fix For: 7.5.0.Final > > > When a list is set as a value in a unary test, it should be checked for containment. Currently the engine checks for equality. > E.g.: in a decision table, if the input expression is "bob" and the input entry in a row is listOfNames, the engine should check if "bob" is an element contained in listOfNames. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3116) Elytron subsystem does not expose digest-sha-384 for digest password

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3116?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3116: ------------------------------------- Issue Type: Enhancement (was: Bug) > Elytron subsystem does not expose digest-sha-384 for digest password > -------------------------------------------------------------------- > > Key: WFCORE-3116 > URL: https://issues.jboss.org/browse/WFCORE-3116 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Affects Versions: 3.0.0.Beta28 > Reporter: Yeray Borges > Assignee: Yeray Borges > Fix For: 4.0.0.Alpha4 > > > For the sake of completeness add digest-sha-384 to allowed values of algorithm attribute of set-password operation > {code:title=/subsystem=elytron/ldap-realm=a:read-operation-description(name=set-password)} > "digest" => { > "type" => OBJECT, > "description" => "A digest password.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "value-type" => { > "algorithm" => { > "type" => STRING, > "description" => "The algorithm used to encrypt the password.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => "digest-sha-512", > "allowed" => [ > "digest-md5", > "digest-sha", > "digest-sha-256", > "digest-sha-512" > ] > }, > "password" => { > "type" => STRING, > "description" => "The actual password to set.", > "expressions-allowed" => false, > "required" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "realm" => { > "type" => STRING, > "description" => "The realm.", > "expressions-allowed" => false, > "required" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > } > } > }, > {code} > Passwords of types otp, salted-simple-digest, simple-digest already expose sha-384 variant. > Seems to me underlying Elytron implementation is already prepared for that. > {code:java|title=DigestPasswordImpl.java} > private static MessageDigest getMessageDigest(final String algorithm) throws NoSuchAlgorithmException { > switch (algorithm) { > case ALGORITHM_DIGEST_MD5: > return MessageDigest.getInstance("MD5"); > case ALGORITHM_DIGEST_SHA: > return MessageDigest.getInstance("SHA-1"); > case ALGORITHM_DIGEST_SHA_256: > return MessageDigest.getInstance("SHA-256"); > case ALGORITHM_DIGEST_SHA_384: > return MessageDigest.getInstance("SHA-384"); > case ALGORITHM_DIGEST_SHA_512: > return MessageDigest.getInstance("SHA-512"); > default: > throw log.noSuchAlgorithmInvalidAlgorithm(algorithm); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-8942: ---------------------------------- Just throwing in a confirmation that this is all now working correctly in Wildfly 11.0.0.Final > Request Scope is not active during Batchlet > ------------------------------------------- > > Key: WFLY-8942 > URL: https://issues.jboss.org/browse/WFLY-8942 > Project: WildFly > Issue Type: Bug > Components: Batch, CDI / Weld > Affects Versions: 10.1.0.Final > Environment: Wildfly 10.1.0 Final > Reporter: Cody Lerum > Assignee: James Perkins > Fix For: 11.0.0.Beta1 > > Attachments: batch-chunk.war > > > When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted. > Example > {noformat} > 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped > at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689) > at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90) > at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165) > at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-40) Misc. code improvements suggested by static analysis

by Luis Barreiro (JIRA)

Luis Barreiro created AG-40: ------------------------------- Summary: Misc. code improvements suggested by static analysis Key: AG-40 URL: https://issues.jboss.org/browse/AG-40 Project: Agroal Issue Type: Enhancement Affects Versions: 0.2 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-39) Deprecate AgroalDataSource.addListener()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-39?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-39. ----------------------------- Resolution: Done > Deprecate AgroalDataSource.addListener() > ---------------------------------------- > > Key: AG-39 > URL: https://issues.jboss.org/browse/AG-39 > Project: Agroal > Issue Type: Enhancement > Components: api > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-39) Deprecate AgroalDataSource.addListener()

by Luis Barreiro (JIRA)

Luis Barreiro created AG-39: ------------------------------- Summary: Deprecate AgroalDataSource.addListener() Key: AG-39 URL: https://issues.jboss.org/browse/AG-39 Project: Agroal Issue Type: Enhancement Components: api Affects Versions: 0.2 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.3 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-109: -------------------------------------- I'm removing the target version for this as we need to figure out a way we can get an SSL context from the Elytron subsystem. There is no point changing the attributes until we allow the transport protocol to be changed. See LOGMGR-177 for some information on how we may handle this in the log manager. > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-109: --------------------------------- Fix Version/s: (was: 4.0.0.Alpha4) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2125) Lists as unary tests should be checked for containment, not equality

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2125?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-2125: -------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Lists as unary tests should be checked for containment, not equality > -------------------------------------------------------------------- > > Key: DROOLS-2125 > URL: https://issues.jboss.org/browse/DROOLS-2125 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Fix For: 7.5.0.Final > > > When a list is set as a value in a unary test, it should be checked for containment. Currently the engine checks for equality. > E.g.: in a decision table, if the input expression is "bob" and the input entry in a row is listOfNames, the engine should check if "bob" is an element contained in listOfNames. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2496: ------------------------------------- Fix Version/s: (was: 4.0.0.Alpha4) I believe this can be closed. WF 11 supports both the vault and credential references to Elytron credential stores. > Functionality in WildFly to encrypt database passwords > ------------------------------------------------------ > > Key: WFCORE-2496 > URL: https://issues.jboss.org/browse/WFCORE-2496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Carlton Zachary > > Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml. > Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2017