September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges edited comment on WFCORE-3321 at 9/29/17 11:01 AM: ---------------------------------------------------------------- [~jcacek] I don't know if QE uses the same technique for wildfly-core. I've checked jboss.dist is not being used for Elytron tests on wildfly-core, please, let me know if you want this issue fixed in wildfly-core too, if not, you can simply close this one. was (Author: yersan): [~jcacek] I don't know if QE uses the same technique for wildfly-core. I've checked jboss.dist is not using for Elytron tests on wildfly-core, please, let me know if you want this issue fixed in wildfly-core too, if not, you can simply close this one. > The jboss.dist system property is not used in testsuite/elytron module > ---------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-3321: --------------------------------- Summary: The jboss.dist system property is not used in testsuite/elytron module (was: The jboss.dist system property is not used in testsuite/integration/elytron module) > The jboss.dist system property is not used in testsuite/elytron module > ---------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/integration/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges commented on WFCORE-3321: -------------------------------------- [~jcacek] I don't know if QE uses the same technique for wildfly-core. I've checked jboss.dist is not using for Elytron tests on wildfly-core, please, let me know if you want this issue fixed in wildfly-core too, if not, you can simply close this one. > The jboss.dist system property is not used in testsuite/integration/elytron module > ---------------------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/integration/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-3321: --------------------------------- Tester: Martin Švehla (was: Josef Cacek) > The jboss.dist system property is not used in testsuite/integration/elytron module > ---------------------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/integration/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-3321: --------------------------------- Tester: Josef Cacek (was: Martin Švehla) > The jboss.dist system property is not used in testsuite/integration/elytron module > ---------------------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/integration/elytron module

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ] Yeray Borges moved JBEAP-13292 to WFCORE-3321: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3321 (was: JBEAP-13292) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: 3.0.3.Final (was: 7.1.0.DR18) Affects Testing: (was: Blocks Testing) > The jboss.dist system property is not used in testsuite/integration/elytron module > ---------------------------------------------------------------------------------- > > Key: WFCORE-3321 > URL: https://issues.jboss.org/browse/WFCORE-3321 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.3.Final > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property. > The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6465) CDI 2.0 Support

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-6465?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-6465: ------------------------------------ For the record: Weld team already provides Weld 3 (CDI 2.0) patches for WildFly (see for example https://github.com/weld/wildfly/tree/11.0.0.CR1-weld3). > CDI 2.0 Support > --------------- > > Key: WFLY-6465 > URL: https://issues.jboss.org/browse/WFLY-6465 > Project: WildFly > Issue Type: Sub-task > Components: CDI / Weld > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9269) Upgrade Weld to 3.0.1.Final (CDI 2.0)

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9269?page=com.atlassian.jira.plugin.... ] Martin Kouba resolved WFLY-9269. -------------------------------- Resolution: Duplicate Issue > Upgrade Weld to 3.0.1.Final (CDI 2.0) > ------------------------------------- > > Key: WFLY-9269 > URL: https://issues.jboss.org/browse/WFLY-9269 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Leandro Kersting de Freitas > Assignee: Martin Kouba > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9269) Upgrade Weld to 3.0.1.Final (CDI 2.0)

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9269?page=com.atlassian.jira.plugin.... ] Martin Kouba reassigned WFLY-9269: ---------------------------------- Assignee: Martin Kouba (was: Stuart Douglas) > Upgrade Weld to 3.0.1.Final (CDI 2.0) > ------------------------------------- > > Key: WFLY-9269 > URL: https://issues.jboss.org/browse/WFLY-9269 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Leandro Kersting de Freitas > Assignee: Martin Kouba > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-978) Remove DEBUG message in server logs while calling isCallerInRole(String roleName) method

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/SECURITY-978?page=com.atlassian.jira.plug... ] Ilia Vassilev moved JBEAP-13291 to SECURITY-978: ------------------------------------------------ Project: PicketBox (was: JBoss Enterprise Application Platform) Key: SECURITY-978 (was: JBEAP-13291) Workflow: classic default workflow (was: CDW with loose statuses v1) > Remove DEBUG message in server logs while calling isCallerInRole(String roleName) method > ---------------------------------------------------------------------------------------- > > Key: SECURITY-978 > URL: https://issues.jboss.org/browse/SECURITY-978 > Project: PicketBox > Issue Type: Bug > Environment: Red Hat JBoss Enterprise Application Platform 7.0.x > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > > While explicitly checking the user roles in the ejb code using context.isCallerInRole(String roleName) and when it return false below exception message got printed at the DEBUG level in server.log file. > {code:java} > 2017-09-13 21:10:24,549 DEBUG [org.jboss.security] sessionhash="b34cb4c5c50e3eefbe4f924ee42fa658" requestid="33015X1505317224509" username="adm2.lg" src_ip="127.0.0.1" PBOX00326: isCallerInRole processing failed: org.jboss.security.authorization.AuthorizationException: PBOX00017: Acces denied: authorization failed > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.invokeAuthorize(JBossAuthorizationContext.java:274) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.access$000(JBossAuthorizationContext.java:71) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext$1.run(JBossAuthorizationContext.java:147) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.authorize(JBossAuthorizationContext.java:143) > at org.jboss.security.plugins.JBossAuthorizationManager.internalAuthorization(JBossAuthorizationManager.java:438) > at org.jboss.security.plugins.JBossAuthorizationManager.authorize(JBossAuthorizationManager.java:115) > at org.jboss.security.plugins.javaee.EJBAuthorizationHelper.isCallerInRole(EJBAuthorizationHelper.java:187) > at org.jboss.as.security.service.SimpleSecurityManager.isCallerInRole(SimpleSecurityManager.java:229) > at org.jboss.as.ejb3.component.EJBComponent.isCallerInRole(EJBComponent.java:400) > at org.jboss.as.ejb3.context.EJBContextImpl.isCallerInRole(EJBContextImpl.java:115) > {code} > The exception seems to be printed in DEBUG in the below line > {code:java} > https://github.com/picketbox/picketbox/blob/master/security-jboss-sx/jbos... > {code} > This should not be logged as an exception message may be just a line in DEBUG logs should be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2017