June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2722) Elytron subsystem - Missing OTP support in set-password operation on identity in filesystem-realm

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2722?page=com.atlassian.jira.plugi... ] Yeray Borges reopened WFCORE-2722: ---------------------------------- > Elytron subsystem - Missing OTP support in set-password operation on identity in filesystem-realm > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-2722 > URL: https://issues.jboss.org/browse/WFCORE-2722 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Yeray Borges > Priority: Critical > Fix For: 3.0.0.Beta24 > > > The set-password operation on identities in filesystem-realm doesn't support OTP credentials. So identity with OneTimePassword can't be created in the filesystem-realm (Elytron subsystem). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-162) WildFly: support logback.xml in Per-deployment Logging (instead of silently ignoring logback.xml)

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created LOGMGR-162: --------------------------------------- Summary: WildFly: support logback.xml in Per-deployment Logging (instead of silently ignoring logback.xml) Key: LOGMGR-162 URL: https://issues.jboss.org/browse/LOGMGR-162 Project: JBoss Log Manager Issue Type: Feature Request Components: core Reporter: Geoffrey De Smet Wildfly currently supports the following _Per deployment logging_ configurations [1]: logging.properties jboss-logging.properties log4j.properties log4j.xml jboss-log4j.xml All of these are stale because they are based on Log4j 1.x format which died about 8 years ago (along with using properties files for logging configuration). Modern popular options include Logback (with SLF4J), JBoss Logging and Log4j 2.x. *I regularly see WildFly users (included RH employees) that struggle to configure the logging configuration of their WildFly apps.* Spring Boot does not have this problem. _To fix this, WildFly should support logback.xml for Per deployment logging too._ When I add a logback.xml in my war's WEB-INF/classes directory and explicitly add the logback-classic.jar in WEB-INF/lib directory - which works to configure Logback in any other JVM - then WildFly ignores it (~ it says GFY). My logs doesn't show up and developing on WildfFly is a pain due to blindness. Fake solution: Configuring the log files per WildFly installation is not practical for developers (it is for sys admins): the log configuration should be in my war's sources on github, so other developers automatically have it without needing to jump to wildfly installation hoops (which is sometimes not possible, think OpenShift). Although it's ok that WildFly favors JBoss Logging, it should not dictate it and support other logging systems such as Logback too for the war files at least (= per deployment). [1] https://docs.jboss.org/author/display/WFLY10/Logging+Configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8979) Upgrade WildFly Transaction Client to 1.0.0.CR2

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8979?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-8979: ------------------------------ Summary: Upgrade WildFly Transaction Client to 1.0.0.CR2 (was: Upgrade WildFly Transaction Client to 1.0.0.CR1) > Upgrade WildFly Transaction Client to 1.0.0.CR2 > ----------------------------------------------- > > Key: WFLY-8979 > URL: https://issues.jboss.org/browse/WFLY-8979 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1625) Kie-server documentation is missing screenshots

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1625?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1625: --------------------------------- Affects Version/s: 7.0.0.Final > Kie-server documentation is missing screenshots > ----------------------------------------------- > > Key: DROOLS-1625 > URL: https://issues.jboss.org/browse/DROOLS-1625 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final > Reporter: Toni Rikkola > Attachments: Screenshot 2017-06-21 10.20.25.png > > > Noticed that there are several "insert screenshot here" place holders in the docs. > !Screenshot 2017-06-21 10.20.25.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1626) Kie-server management: Pressing upgrade throws an error

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1626?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1626: --------------------------------- Affects Version/s: 7.0.0.Final > Kie-server management: Pressing upgrade throws an error > ------------------------------------------------------- > > Key: DROOLS-1626 > URL: https://issues.jboss.org/browse/DROOLS-1626 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final > Reporter: Toni Rikkola > Assignee: Edson Tirelli > > I have kie-server and workbench running on the same Wildfly. > The project deploys to kie-server correctly and runs ok. > Using the KIE workbench kie-server management. > When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1626) Kie-server management: Pressing upgrade throws an error

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1626?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1626: --------------------------------- Description: I have kie-server and workbench running on the same Wildfly. The project deploys to kie-server correctly and runs ok. Using the KIE workbench kie-server management. When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. was: I have kie-server and workbench running on the same Wildfly. The project deploys to kie-server correctly and runs ok. When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. > Kie-server management: Pressing upgrade throws an error > ------------------------------------------------------- > > Key: DROOLS-1626 > URL: https://issues.jboss.org/browse/DROOLS-1626 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Edson Tirelli > > I have kie-server and workbench running on the same Wildfly. > The project deploys to kie-server correctly and runs ok. > Using the KIE workbench kie-server management. > When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1257) Remove credentials key-pair and public-key-pem from Elytron client configuration file

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1257: --------------------------------- Summary: Remove credentials key-pair and public-key-pem from Elytron client configuration file Key: ELY-1257 URL: https://issues.jboss.org/browse/ELY-1257 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Based on following discussion with [~dmlloyd]: {quote} > - key-pair - what is the reason for this credential element? How it can be used? This is for key-based authentication mechanisms, like SSH. We're also developing a key-based SASL mechanism [1] that will hopefully make some progress in the next quarter (and is open to contribution from all). > - public-key-pem - I do not understand reason of this credentials on client side. I would be able to understand private-key-pem. Is this element correct or should be removed? A public key could be used for the purposes of server verification. We don't yet have a way to establish a means to authenticate servers though, other than using a trust store; this is something that will probably be developed in conjunction with [1]. [1] https://github.com/dmlloyd/pk-rfc {quote} we suggest to remove {{key-pair}} and {{public-key-pem}} from {{configuration.authentication-client.authentication-configurations.configuration.credentials}} in Elytron client configuration file. We can introduce those credentials once it will be implemented. Provided credentials for mechanisms which are currently not supported in Elytron can be confusing and can result in incorrect client configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1626) Kie-server management: Pressing upgrade throws an error

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-1626: ------------------------------------ Summary: Kie-server management: Pressing upgrade throws an error Key: DROOLS-1626 URL: https://issues.jboss.org/browse/DROOLS-1626 Project: Drools Issue Type: Bug Reporter: Toni Rikkola Assignee: Edson Tirelli I have kie-server and workbench running on the same Wildfly. The project deploys to kie-server correctly and runs ok. When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1257) Remove credentials key-pair and public-key-pem from Elytron client configuration file

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1257?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1257: ------------------------------ Affects Version/s: 1.1.0.Beta52 > Remove credentials key-pair and public-key-pem from Elytron client configuration file > ------------------------------------------------------------------------------------- > > Key: ELY-1257 > URL: https://issues.jboss.org/browse/ELY-1257 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > Based on following discussion with [~dmlloyd]: > {quote} > > - key-pair - what is the reason for this credential element? How it can be used? > This is for key-based authentication mechanisms, like SSH. We're also > developing a key-based SASL mechanism [1] that will hopefully make some > progress in the next quarter (and is open to contribution from all). > > - public-key-pem - I do not understand reason of this credentials on client side. I would be able to understand private-key-pem. Is this element correct or should be removed? > A public key could be used for the purposes of server verification. We > don't yet have a way to establish a means to authenticate servers > though, other than using a trust store; this is something that will > probably be developed in conjunction with [1]. > [1] https://github.com/dmlloyd/pk-rfc > {quote} > we suggest to remove {{key-pair}} and {{public-key-pem}} from {{configuration.authentication-client.authentication-configurations.configuration.credentials}} in Elytron client configuration file. We can introduce those credentials once it will be implemented. Provided credentials for mechanisms which are currently not supported in Elytron can be confusing and can result in incorrect client configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1625) Kie-server documentation is missing screenshots

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1625?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1625: --------------------------------- Description: Noticed that there are several "add screenshot here" place holders in the docs. !Screenshot 2017-06-21 10.20.25.png|thumbnail! was: Noticed that there are several "add screenshot here" place holders in the docs. > Kie-server documentation is missing screenshots > ----------------------------------------------- > > Key: DROOLS-1625 > URL: https://issues.jboss.org/browse/DROOLS-1625 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Attachments: Screenshot 2017-06-21 10.20.25.png > > > Noticed that there are several "add screenshot here" place holders in the docs. > !Screenshot 2017-06-21 10.20.25.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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