March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2545) Principal with null name causes hidden NPE for chained-principal-transformer

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-2545: ------------------------------------ Summary: Principal with null name causes hidden NPE for chained-principal-transformer Key: WFCORE-2545 URL: https://issues.jboss.org/browse/WFCORE-2545 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical In case when Principal with null name is used in {{chain}} of {{org.wildfly.extension.elytron.capabilities.PrincipalTransformer}} then this method throw NullPointerException which is hidden to user due to JBEAP-9625. This issue can be simply reproduced by using regex-validating-principal-transformer and user which does not match given pattern. Then Principal name is set to null which results to following NPE: {code} java.lang.NullPointerException: java.util.regex.Matcher.getTextLength(Matcher.java:1283) java.util.regex.Matcher.reset(Matcher.java:309) java.util.regex.Matcher.<init>(Matcher.java:229) java.util.regex.Pattern.matcher(Pattern.java:1093) org.wildfly.security.auth.util.RegexNameRewriter.rewriteName(RegexNameRewriter.java:55) org.wildfly.security.auth.server.NameRewriter.lambda$asPrincipalRewriter$1(NameRewriter.java:63) org.wildfly.extension.elytron.capabilities.PrincipalTransformer.lambda$chain$1(PrincipalTransformer.java:64) ... {code} Since there is no related documentation or javadoc it is also possible that issue is rather in regex-validating-principal-transformer which could set Principal to null instead of Principal name to null. It must be clarified by engineering. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1007) Exception in authenticate() method of SecurityContextImpl is hidden

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1007: --------------------------------- Summary: Exception in authenticate() method of SecurityContextImpl is hidden Key: ELY-1007 URL: https://issues.jboss.org/browse/ELY-1007 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical In case when {{authenticator.authenticate()}} in {{authenticate()}} method of {{org.wildfly.elytron.web.undertow.server.SecurityContextImpl}} [1] throws exception, then this exception is hidden and only internal server error status is returned. Thrown exception should be logged. This issue can be cause of JBEAP-9377. [1] https://github.com/wildfly-security/elytron-web/blob/49241df4afcc37158c54... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-70) Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-70?page=com.atlassian.jira.plu... ] Sunil kondkar commented on HAWKULARQE-70: ----------------------------------------- 1) Created scripts: Commits: https://github.com/Hawkular-QE/cf-ui/compare/dockerscripts 2) Created new CFME instance for test on openstack (to be able to use yum and git): 10.8.184.58 3) Configured Jenkins Job to experiment: http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/miq-ms-cfui-nightly-... -Added ssh site 10.8.184.58 to Jenkins global configuration and tested that the instance can be ssh'ed -Added commands in jenkins job to git clone and check URL if working correctly (This is under test and working partly) PR to be sent once all tests pass. > Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server > --------------------------------------------------------------------------------- > > Key: HAWKULARQE-70 > URL: https://issues.jboss.org/browse/HAWKULARQE-70 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Need of the task: > To make sure the CFME docker instance that we use on Jenkins nightly run has CFME containers always running, we use docker scripts. > These are existing shell scripts which are using old methods to create cfme docker container and then start the cfme instance which are irrelevant now: > These are located at: > https://github.com/Hawkular-QE/cf-ui/tree/master/scripts/automation/docker > This task is to: > 1) Modify the scripts (common.sh, start.sh) to: > -Stop the CFME instance > -Start the CFME instance > -Check if the URL is ready using curl > -Check the logs if CFME is started > 2) Git clone the modified scripts to CFME server > 3) Execute the scripts on CFME server > ( Use 'execute shell script' on Jenkins nightly job to ssh/git clone and execute script on CFME server) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1006) Elytron Audit Logging does not support log file rotation

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-1006?page=com.atlassian.jira.plugin.s... ] Jan Tymel reassigned ELY-1006: ------------------------------ Assignee: (was: Darran Lofthouse) > Elytron Audit Logging does not support log file rotation > -------------------------------------------------------- > > Key: ELY-1006 > URL: https://issues.jboss.org/browse/ELY-1006 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Tymel > Priority: Blocker > Attachments: deployment.war > > > It is not possible to rotate (= rename current log file and start logging into a new one) Elytron Audit log files. It cannot be set to use the log rotation neither based on the file size (e.g. once the file size outreaches 100 MB) nor based on a time period (e.g. rotate create a new file every Sunday at midnight). > Inability to set the log rotation could lead to huge log files. Then it would be really difficult to read such files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1006) Elytron Audit Logging does not support log file rotation

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-1006?page=com.atlassian.jira.plugin.s... ] Jan Tymel updated ELY-1006: --------------------------- Attachment: deployment.war > Elytron Audit Logging does not support log file rotation > -------------------------------------------------------- > > Key: ELY-1006 > URL: https://issues.jboss.org/browse/ELY-1006 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Tymel > Priority: Blocker > Attachments: deployment.war > > > It is not possible to rotate (= rename current log file and start logging into a new one) Elytron Audit log files. It cannot be set to use the log rotation neither based on the file size (e.g. once the file size outreaches 100 MB) nor based on a time period (e.g. rotate create a new file every Sunday at midnight). > Inability to set the log rotation could lead to huge log files. Then it would be really difficult to read such files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1006) Elytron Audit Logging does not support log file rotation

by Jan Tymel (JIRA)

Jan Tymel created ELY-1006: ------------------------------ Summary: Elytron Audit Logging does not support log file rotation Key: ELY-1006 URL: https://issues.jboss.org/browse/ELY-1006 Project: WildFly Elytron Issue Type: Bug Reporter: Jan Tymel Assignee: Darran Lofthouse Priority: Blocker It is not possible to rotate (= rename current log file and start logging into a new one) Elytron Audit log files. It cannot be set to use the log rotation neither based on the file size (e.g. once the file size outreaches 100 MB) nor based on a time period (e.g. rotate create a new file every Sunday at midnight). Inability to set the log rotation could lead to huge log files. Then it would be really difficult to read such files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-72?page=com.atlassian.jira.plu... ] Sunil kondkar reassigned HAWKULARQE-72: --------------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Polarion data cleanup > --------------------- > > Key: HAWKULARQE-72 > URL: https://issues.jboss.org/browse/HAWKULARQE-72 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Task to able to have polarion reports in place. > Reports: > 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 3) Test Run Status by Plan > 4) Test Run Status by Plan and chosen fields > Tasks: > 1) Find and remove duplicates > 2) Each test case has correct fields > -Description > - Level > - Test type and sub type > - Automated or Manual > - Importance (Severity) > 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) > Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans > 4) Check if manual test cases are with approved status( Approve if needed) > 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. > (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

Sunil kondkar created HAWKULARQE-72: --------------------------------------- Summary: Polarion data cleanup Key: HAWKULARQE-72 URL: https://issues.jboss.org/browse/HAWKULARQE-72 Project: Hawkular QE Issue Type: Task Reporter: Sunil kondkar Assignee: Michael Foley Task to able to have polarion reports in place. Reports: 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... 3) Test Run Status by Plan 4) Test Run Status by Plan and chosen fields Tasks: 1) Find and remove duplicates 2) Each test case has correct fields -Description - Level - Test type and sub type - Automated or Manual - Importance (Severity) 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans 4) Check if manual test cases are with approved status( Approve if needed) 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6842) Impossible to read/configure messaging provider journal directory path

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-6842?page=com.atlassian.jira.plugin.... ] Claudio Miranda closed WFLY-6842. --------------------------------- Resolution: Done As HAL-1137 is resolved, this should be resolved too. > Impossible to read/configure messaging provider journal directory path > ---------------------------------------------------------------------- > > Key: WFLY-6842 > URL: https://issues.jboss.org/browse/WFLY-6842 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Bartosz Baranowski > Assignee: Michal Petrov > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5504) Servers are missing in the list of servers in a server group in the web console

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-5504?page=com.atlassian.jira.plugin.... ] Claudio Miranda closed WFLY-5504. --------------------------------- Assignee: Claudio Miranda (was: Heiko Braun) Resolution: Cannot Reproduce Bug Cannot reproduce the problem, if you feel this is wrong, reopen please. > Servers are missing in the list of servers in a server group in the web console > ------------------------------------------------------------------------------- > > Key: WFLY-5504 > URL: https://issues.jboss.org/browse/WFLY-5504 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.0.0.CR2 > Environment: Debian 8, Java 8u60, wildfly 10.0.0.CR2 in domain mode > Reporter: Thiago Presa > Assignee: Claudio Miranda > Attachments: bug1.png, bug3.png, bug4.png > > > I created a server-group for an application in a wildfly running in domain mode. This wildfly cluster is composed of a master node and two slave nodes. > I then created two servers in this server group in the two slave nodes. > When I ask through the web console to view details of those servers, they show up correctly: > !bug1.png|thumbnail! > !bug4.png|thumbnail! > However, when listing the servers in the cdl server group, only one of them is listed: > !bug3.png|thumbnail! > As far as I've checked, XMLs are OK, there are no Exceptions in the logs and the application is running fine. Please let me know if further info is necessary. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017