April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3753) Support Logging in the embedded server

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-3753: ----------------------------------- Summary: Support Logging in the embedded server Key: WFCORE-3753 URL: https://issues.jboss.org/browse/WFCORE-3753 Project: WildFly Core Issue Type: Feature Request Components: Embedded, Logging Reporter: James Perkins Assignee: James Perkins When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3205: -------------------------------- Issue Type: Feature Request (was: Enhancement) > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Feature Request > Components: Embedded, Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10257) Cannot add non-anonymous entries to authentication configuration via console

by David Lloyd (JIRA)

David Lloyd created WFLY-10257: ---------------------------------- Summary: Cannot add non-anonymous entries to authentication configuration via console Key: WFLY-10257 URL: https://issues.jboss.org/browse/WFLY-10257 Project: WildFly Issue Type: Bug Components: Web Console Reporter: David Lloyd Assignee: Harald Pehl If you try to add an authentication configuration which includes an authentication-name (i.e. is not anonymous), you get an error because the "anonymous" attribute is present even though it is not valid due to the use of alternatives. This appears to be a realization of a more general problem handling alternative attribute sets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10257) Cannot add non-anonymous entries to authentication configuration via console

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10257?page=com.atlassian.jira.plugin... ] David Lloyd updated WFLY-10257: ------------------------------- Priority: Critical (was: Major) > Cannot add non-anonymous entries to authentication configuration via console > ---------------------------------------------------------------------------- > > Key: WFLY-10257 > URL: https://issues.jboss.org/browse/WFLY-10257 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: David Lloyd > Assignee: Harald Pehl > Priority: Critical > > If you try to add an authentication configuration which includes an authentication-name (i.e. is not anonymous), you get an error because the "anonymous" attribute is present even though it is not valid due to the use of alternatives. > This appears to be a realization of a more general problem handling alternative attribute sets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-23) Cucushift Tests for Swift Sunshine

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-23?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo updated SWSQE-23: ----------------------------------------- Sprint: (was: Kiali QE Sprint 4) > Cucushift Tests for Swift Sunshine > ----------------------------------- > > Key: SWSQE-23 > URL: https://issues.jboss.org/browse/SWSQE-23 > Project: Kiali QE > Issue Type: Epic > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1564) In PasswordKeyMapper an exception is logged with a wrong algorithm name.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1564?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1564: ------------------------------- Description: In PasswordKeyMapper an exception is logged with the default algorithm name instead of the algorithm used to instantiate PasswordFactory object. {code:java|title=PasswordKeyMapper.java} final PasswordFactory passwordFactory; try { passwordFactory = PasswordFactory.getInstance(algorithmName, providers); } catch (NoSuchAlgorithmException e) { throw log.couldNotObtainPasswordFactoryForAlgorithm(algorithmName, e); } ... try { Password password = passwordFactory.generatePassword(passwordSpec); if (log.isTraceEnabled()) { log.tracef("Key Mapper: Password credential created using algorithm column value [%s]", algorithmName); } return new PasswordCredential(password); } catch (InvalidKeySpecException e) { throw log.invalidPasswordKeySpecificationForAlgorithm(this.defaultAlgorithm, e); } {code} was: In PasswordKeyMapper an exception is logged with the default algorithm name instead of the algorithm used to instantiate PasswordFactory object. {code} final PasswordFactory passwordFactory; try { passwordFactory = PasswordFactory.getInstance(algorithmName, providers); } catch (NoSuchAlgorithmException e) { throw log.couldNotObtainPasswordFactoryForAlgorithm(algorithmName, e); } {code} ... {code} try { Password password = passwordFactory.generatePassword(passwordSpec); if (log.isTraceEnabled()) { log.tracef("Key Mapper: Password credential created using algorithm column value [%s]", algorithmName); } return new PasswordCredential(password); } catch (InvalidKeySpecException e) { throw log.invalidPasswordKeySpecificationForAlgorithm(this.defaultAlgorithm, e); } {code} > In PasswordKeyMapper an exception is logged with a wrong algorithm name. > ------------------------------------------------------------------------ > > Key: ELY-1564 > URL: https://issues.jboss.org/browse/ELY-1564 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.4.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Minor > > In PasswordKeyMapper an exception is logged with the default algorithm name instead of the algorithm used to instantiate PasswordFactory object. > {code:java|title=PasswordKeyMapper.java} > final PasswordFactory passwordFactory; > try { > passwordFactory = PasswordFactory.getInstance(algorithmName, providers); > } catch (NoSuchAlgorithmException e) { > throw log.couldNotObtainPasswordFactoryForAlgorithm(algorithmName, e); > } > ... > try { > Password password = passwordFactory.generatePassword(passwordSpec); > if (log.isTraceEnabled()) { > log.tracef("Key Mapper: Password credential created using algorithm column value [%s]", algorithmName); > } > return new PasswordCredential(password); > } catch (InvalidKeySpecException e) { > throw log.invalidPasswordKeySpecificationForAlgorithm(this.defaultAlgorithm, e); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1564) In PasswordKeyMapper an exception is logged with a wrong algorithm name.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-1564: ---------------------------------- Summary: In PasswordKeyMapper an exception is logged with a wrong algorithm name. Key: ELY-1564 URL: https://issues.jboss.org/browse/ELY-1564 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms Affects Versions: 1.2.4.Final Reporter: Ilia Vassilev Assignee: Ilia Vassilev Priority: Minor In PasswordKeyMapper an exception is logged with the default algorithm name instead of the algorithm used to instantiate PasswordFactory object. {code} final PasswordFactory passwordFactory; try { passwordFactory = PasswordFactory.getInstance(algorithmName, providers); } catch (NoSuchAlgorithmException e) { throw log.couldNotObtainPasswordFactoryForAlgorithm(algorithmName, e); } {code} ... {code} try { Password password = passwordFactory.generatePassword(passwordSpec); if (log.isTraceEnabled()) { log.tracef("Key Mapper: Password credential created using algorithm column value [%s]", algorithmName); } return new PasswordCredential(password); } catch (InvalidKeySpecException e) { throw log.invalidPasswordKeySpecificationForAlgorithm(this.defaultAlgorithm, e); } {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-146) Decide One Method To Deploy Istio

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-146?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-146. ----------------------------------------- Resolution: Out of Date > Decide One Method To Deploy Istio > --------------------------------- > > Key: SWSQE-146 > URL: https://issues.jboss.org/browse/SWSQE-146 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > > As an automation engineer, I want to deploy Istio in the way that the end user will do so. I do NOT want multiple methods to deploy Istio, unless there is a technical reason to do so. > Decide if QE will continue to use/support installing Istio in it's two current deployment methods, or to deploy in one method: > - The "Mazz" Hack deploy script (current CD) > - Ansible Deploy -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-146) Decide One Method To Deploy Istio

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-146?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-146: ----------------------------------------------- I'm closing the story because booth options are going to be merged into one pipeline > Decide One Method To Deploy Istio > --------------------------------- > > Key: SWSQE-146 > URL: https://issues.jboss.org/browse/SWSQE-146 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > > As an automation engineer, I want to deploy Istio in the way that the end user will do so. I do NOT want multiple methods to deploy Istio, unless there is a technical reason to do so. > Decide if QE will continue to use/support installing Istio in it's two current deployment methods, or to deploy in one method: > - The "Mazz" Hack deploy script (current CD) > - Ansible Deploy -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-2250: ----------------------------------- Assignee: Jozef Marko (was: Michael Anstis) > Align Engine hints in Decision Table column wizard with BAPL-708 > ---------------------------------------------------------------- > > Key: DROOLS-2250 > URL: https://issues.jboss.org/browse/DROOLS-2250 > Project: Drools > Issue Type: Task > Components: Guided Decision Table Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.6.0.Final > > Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png > > > Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc. > [edited] > Also the Data Object designer affected, see the role hint. > !Screenshot from 2018-01-19 14-35-50.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 April 2018