March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1764) Get all Provider implementations moved to their own module.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1764?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1764: ------------------------------------- Assignee: Diana Vilkolakova > Get all Provider implementations moved to their own module. > ----------------------------------------------------------- > > Key: ELY-1764 > URL: https://issues.jboss.org/browse/ELY-1764 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Diana Vilkolakova > Priority: Blocker > > Generally it was the authentication client and it's XML parser that needed to be able to load all Elytron Providers so we hard coded Provider resolution. > We have a couple of alternative options: - > # Hard code the class names in the authentication client and attempt to load 'best efforts' > # Load using ServiceLoader discovery but sort them into the correct position. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1772) Release WildFly Elytron 2.0.0.Alpha2

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1772: ------------------------------------- Summary: Release WildFly Elytron 2.0.0.Alpha2 Key: ELY-1772 URL: https://issues.jboss.org/browse/ELY-1772 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.0.0.Alpha2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3608. ------------------------------------ Resolution: Done This is closed > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1771) Release WildFly Elytron 1.9.0.CR1

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1771: ------------------------------------- Summary: Release WildFly Elytron 1.9.0.CR1 Key: ELY-1771 URL: https://issues.jboss.org/browse/ELY-1771 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Klara Kufova reopened DROOLS-3608: ---------------------------------- Reopening. > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Klara Kufova edited comment on DROOLS-3608 at 3/20/19 9:50 AM: --------------------------------------------------------------- [~gabriolo], this shouldn't be closed, correct? was (Author: kkufova): Reopening. > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3780) DMN DT Analysis report warn for HitPolicy First

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3780?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3780: ----------------------------------- Sprint: 2019 Week 11-13 > DMN DT Analysis report warn for HitPolicy First > ----------------------------------------------- > > Key: DROOLS-3780 > URL: https://issues.jboss.org/browse/DROOLS-3780 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > {quote}"First" hit policy decision tables are not considered good practice because they do not offer a clear overview of the decision logic > {quote} > (quoted from: Decision Model and Notation specification) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11881) Upgrade WildFly Core 9.0.0.Beta1

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-11881: ---------------------------------- Summary: Upgrade WildFly Core 9.0.0.Beta1 Key: WFLY-11881 URL: https://issues.jboss.org/browse/WFLY-11881 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-629) Enabled automatic encryption of passwords stored in configuration

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-629?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFCORE-629: ------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Enabled automatic encryption of passwords stored in configuration > ----------------------------------------------------------------- > > Key: WFCORE-629 > URL: https://issues.jboss.org/browse/WFCORE-629 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Environment: Wildfly 9 > Reporter: Jason Shepherd > Assignee: Darran Lofthouse > Priority: Major > Fix For: 9.0.0.Beta2 > > > Currently encrypting passwords such as Datasource passwords can only be done 'after the fact'. You have to create the datasource first, then retrospectively store the password in the vault and dereference it in the configuration. > It would be great if could turn on automatic storage of passwords in the vault so that when you create a Datasource password, or add a resource adapter which specifies a remote resource password, those passwords were automatically added to the vault, and deferenced in the configuration file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3832) Support hex encoding in jdbc-realm for elytron

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3832: -------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: WFCORE-3832 > URL: https://issues.jboss.org/browse/WFCORE-3832 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Major > Labels: elytron > Fix For: 9.0.0.Beta2 > > > Old database login-module can be configured passing the attribute {{hashEncoding}}, for example: > {code:xml} > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> > <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> > <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> > <module-option name="hashAlgorithm" value="SHA-1"/> > <module-option name="hashEncoding" value="hex"/> > <module-option name="hashCharset" value="UTF-8"/> > </login-module> > {code} > Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron. > Think also about the charset attribute. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 2019