March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2566) Subsystem parsing tests ignores wrong END_ELEMENT

by Jan Kalina (JIRA)

Jan Kalina created WFCORE-2566: ---------------------------------- Summary: Subsystem parsing tests ignores wrong END_ELEMENT Key: WFCORE-2566 URL: https://issues.jboss.org/browse/WFCORE-2566 Project: WildFly Core Issue Type: Bug Reporter: Jan Kalina Assignee: Jan Kalina Priority: Minor Tests based on *AbstractSubsystemBaseTest* ignores bugs like excessive {code}requireNoContent(reader);{code} Tests will fail only if some next element follows - its parsing fails in such case correctly. Would be better to add same check in the end of *<test>* parsing, which would check not only there is END_ELEMENT, but also that its name really equals *test*. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1017) Release WildFly Elytron 1.0.4.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1017?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1017. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.0.4.Final > ----------------------------------- > > Key: ELY-1017 > URL: https://issues.jboss.org/browse/ELY-1017 > Project: WildFly Elytron > Issue Type: Release > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1017) Release WildFly Elytron 1.0.4.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1017?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1017: ---------------------------------- Summary: Release WildFly Elytron 1.0.4.Final (was: Release WildFly Elytron 1.0.0.Beta4) > Release WildFly Elytron 1.0.4.Final > ----------------------------------- > > Key: ELY-1017 > URL: https://issues.jboss.org/browse/ELY-1017 > Project: WildFly Elytron > Issue Type: Release > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-647) MechanismDatabase create SSL_ aliases incompletely

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-647?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-647: --------------------------------- Fix Version/s: 1.0.4.CR1 1.1.0.Beta10 > MechanismDatabase create SSL_ aliases incompletely > -------------------------------------------------- > > Key: ELY-647 > URL: https://issues.jboss.org/browse/ELY-647 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.1.0.Beta10, 1.0.4.CR1 > > > SSL MechanismDatabase should create alias for every TLS_* from SSL_*. It create them only for direct entries, not for other aliases. > MechanismDatabase.properties contains for example: > {code:java} > TLS_RSA_FIPS_WITH_3DES_EDE_CBC_SHA = alias:TLS_RSA_WITH_3DES_EDE_CBC_SHA > {code} > The *TLS_RSA_FIPS_WITH_3DES_EDE_CBC_SHA* works ok, but *SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA* doesnt exist. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1017) Release WildFly Elytron 1.0.0.Beta4

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1017: ------------------------------------- Summary: Release WildFly Elytron 1.0.0.Beta4 Key: ELY-1017 URL: https://issues.jboss.org/browse/ELY-1017 Project: WildFly Elytron Issue Type: Release Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.4.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2565?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2565: --------------------------------- Affects Version/s: 3.0.0.Beta9 > Incorrect permission class-name should throw exception at runtime > ----------------------------------------------------------------- > > Key: WFCORE-2565 > URL: https://issues.jboss.org/browse/WFCORE-2565 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-2565: ------------------------------------ Summary: Incorrect permission class-name should throw exception at runtime Key: WFCORE-2565 URL: https://issues.jboss.org/browse/WFCORE-2565 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2565?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2565: --------------------------------- Steps to Reproduce: Add non-existent permission into default-permission-mapper: {code} /subsystem=elytron/constant-permission-mapper=default-permission-mapper:write-attribute(name=permissions[4],value={class-name=WrongName}) {code} and use this mapper at runtime. No exception is thrown. was: Add non-existent permission into default {default-permission-mapper}: {code} /subsystem=elytron/constant-permission-mapper=default-permission-mapper:write-attribute(name=permissions[4],value={class-name=WrongName}) {code} and use this mapper at runtime. No exception is thrown. > Incorrect permission class-name should throw exception at runtime > ----------------------------------------------------------------- > > Key: WFCORE-2565 > URL: https://issues.jboss.org/browse/WFCORE-2565 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime. -- 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: ----------------------------------------- -CF-UI Docker Scripts are modified to stop, remove and then create a new CFME container. -Configured the Jenkins job with Shell scripts to git clone and then execute docker scripts on test environment to stop, remove and then create a new CFME container. -Jenkins job: http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/miq-ms-cfui-nightly-... -The Jenkins slave node is now configured to be able to show vnc using: vncviewer 10.8.184.19:5906 -The Jenkins job is pass on the branch where scripts are committed: Branch: https://github.com/Hawkular-QE/cf-ui/tree/dockerscripts Test runs: http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/miq-ms-cfui-nightly-... http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/job/miq-ms-cfui-nightly-... PR: https://github.com/Hawkular-QE/cf-ui/pull/149 > 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] (WFCORE-2564) Customize resolve-path handle to handle absolute paths

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-2564: ----------------------------------- Summary: Customize resolve-path handle to handle absolute paths Key: WFCORE-2564 URL: https://issues.jboss.org/browse/WFCORE-2564 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Beta9 Reporter: Jeff Mesnil Assignee: Brian Stansberry The :resolve-path operation will always resolve the path based on the relative-to attribute. In the messaging subsystem, we have a different behaviour where the relative-to attribute is *ignored* (whether it is defined or not) when the path value correponds to an absolute path. To be consistent with this behaviour, the :resolve-path operation builder would need customization and specify that the relative-to attribute must be ignored when the path is absolute. -- 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