August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-96) MP Health - security enabled, no user yed added, user get info about adding user to access web console

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-96: -------------------------------------- Summary: MP Health - security enabled, no user yed added, user get info about adding user to access web console Key: WFWIP-96 URL: https://issues.jboss.org/browse/WFWIP-96 Project: WildFly WIP Issue Type: Bug Components: MP Health Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Priority: Minor I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server Note: I didn't add user via {{bin/add-user.sh}} When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console: {code} <h3>Your WildFly Application Server is running.</h3> <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able to access the admin console.</p> <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of your WildFly installation and enter the requested information.</p> {code} Can /health endpoint get customized response in case no mgmt user is defined on server side ? Current response can be little confusing is user is not yet so familiar with WildFly. I marked this as minor bug. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-82) MP Health endpoint forces authentication ATM, spec violation

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-82?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda resolved WFWIP-82. ------------------------------------ Release Notes Text: Resolved via https://github.com/wildfly/wildfly-core/pull/3427 Resolution: Done > MP Health endpoint forces authentication ATM, spec violation > ------------------------------------------------------------ > > Key: WFWIP-82 > URL: https://issues.jboss.org/browse/WFWIP-82 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > MP Health endpoint forces authentication ATM, this is spec violation. > {code} > Security > Aspects regarding the secure access of health check information. > • A producer MAY support security on all health check invocations (i.e. authentication) > • A producer MUST not enforce security by default, it SHOULD be an opt-in feature (i.e. configuration change) > {code} > Already discussed with Jeff, for tracing purposes mainly. > We can use this for discussion about implementation (and model changes) of opt-in feature to enable authentication. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-82) MP Health endpoint forces authentication ATM, spec violation

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-82?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda closed WFWIP-82. ---------------------------------- > MP Health endpoint forces authentication ATM, spec violation > ------------------------------------------------------------ > > Key: WFWIP-82 > URL: https://issues.jboss.org/browse/WFWIP-82 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > MP Health endpoint forces authentication ATM, this is spec violation. > {code} > Security > Aspects regarding the secure access of health check information. > • A producer MAY support security on all health check invocations (i.e. authentication) > • A producer MUST not enforce security by default, it SHOULD be an opt-in feature (i.e. configuration change) > {code} > Already discussed with Jeff, for tracing purposes mainly. > We can use this for discussion about implementation (and model changes) of opt-in feature to enable authentication. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4014) Truststore re-initialization not implemented correctly

by Jan Kalina (JIRA)

Jan Kalina created WFCORE-4014: ---------------------------------- Summary: Truststore re-initialization not implemented correctly Key: WFCORE-4014 URL: https://issues.jboss.org/browse/WFCORE-4014 Project: WildFly Core Issue Type: Bug Reporter: Jan Kalina Assignee: Jan Kalina Priority: Critical WFCORE-3970 (including test) was not implemented correctly - the delegating object should ensure the trustmanager will be changed also for sslcontext, which already keeps reference to the trustmanager. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2870) [DMN Designer] Can not build project with multiple models

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2870?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2870: -------------------------------- Description: If the project contains multiple dmn models, it can not be built. h3. Manual acceptance test - Prepare three models -- Empty -- Just graph nodes -- Login inside graph nodes - Check Deployment successful (/) was: If the project contains multiple dmn models, it can not be built. h3. Manual acceptance test - Prepare three models -- Empty -- Just graph nodes -- Login inside graph nodes - Check Deployment successful > [DMN Designer] Can not build project with multiple models > --------------------------------------------------------- > > Key: DROOLS-2870 > URL: https://issues.jboss.org/browse/DROOLS-2870 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-08-09 10-20-16.png > > > If the project contains multiple dmn models, it can not be built. > h3. Manual acceptance test > - Prepare three models > -- Empty > -- Just graph nodes > -- Login inside graph nodes > - Check Deployment successful (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2870) [DMN Designer] Can not build project with multiple models

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2870?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2870: -------------------------------- Description: If the project contains multiple dmn models, it can not be built. h3. Manual acceptance test - Prepare three models -- Empty -- Just graph nodes -- Login inside graph nodes - Check Deployment successful was:If the project contains multiple dmn models, it can not be built. > [DMN Designer] Can not build project with multiple models > --------------------------------------------------------- > > Key: DROOLS-2870 > URL: https://issues.jboss.org/browse/DROOLS-2870 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-08-09 10-20-16.png > > > If the project contains multiple dmn models, it can not be built. > h3. Manual acceptance test > - Prepare three models > -- Empty > -- Just graph nodes > -- Login inside graph nodes > - Check Deployment successful -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-199) Reinitialize the output stream when it fails on Windows

by Teresa Miyar (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-199?page=com.atlassian.jira.plugin... ] Teresa Miyar commented on LOGMGR-199: ------------------------------------- I'm also trying to duplicate, on windows 10 it does not happen or I was not able to reproduce it there, I've installed today windows 2012 that is were the problem was reported, I will let you know the results. > Reinitialize the output stream when it fails on Windows > ------------------------------------------------------- > > Key: LOGMGR-199 > URL: https://issues.jboss.org/browse/LOGMGR-199 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 2.0.8.Final, 2.1.0.Final > Reporter: Teresa Miyar > Assignee: James Perkins > > After the fix https://issues.jboss.org/browse/LOGMGR-154 we can still observe that the log file when using periodic file size rotation on Windows it stops logging, one solution discussed is to reinitialize the output stream when this happens. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Ning Zhang (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Ning Zhang updated JASSIST-267: ------------------------------- Git Pull Request: https://github.com/jboss-javassist/javassist/pull/210 > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Ning Zhang (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Ning Zhang commented on JASSIST-267: ------------------------------------ New pull request: https://github.com/jboss-javassist/javassist/pull/210 > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10415) Upgrade to ironjacamar 1.4.10 Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10415?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10415: -------------------------------------- Is there a reason for this and the 1.4.11.Final release (WFLY-10675)? > Upgrade to ironjacamar 1.4.10 Final > ----------------------------------- > > Key: WFLY-10415 > URL: https://issues.jboss.org/browse/WFLY-10415 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018