March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8273) Upgrade to WildFly Naming Client 1.0.0.Beta12

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-8273?page=com.atlassian.jira.plugin.... ] Ivo Studensky reassigned WFLY-8273: ----------------------------------- Assignee: David Lloyd (was: Farah Juma) > Upgrade to WildFly Naming Client 1.0.0.Beta12 > --------------------------------------------- > > Key: WFLY-8273 > URL: https://issues.jboss.org/browse/WFLY-8273 > Project: WildFly > Issue Type: Component Upgrade > Components: Naming > Reporter: Ivo Studensky > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8273) Upgrade to WildFly Naming Client 1.0.0.Beta12

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8273: ----------------------------------- Summary: Upgrade to WildFly Naming Client 1.0.0.Beta12 Key: WFLY-8273 URL: https://issues.jboss.org/browse/WFLY-8273 Project: WildFly Issue Type: Component Upgrade Components: Naming Reporter: Ivo Studensky Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1351) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1351?page=com.atlassian.jira.plugi... ] Ivo Studensky commented on WFCORE-1351: --------------------------------------- This issue needs another component upgrade, see WFNC-23. > FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1351 > URL: https://issues.jboss.org/browse/WFCORE-1351 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Security > Reporter: Ondrej Kotek > Assignee: Ivo Studensky > Priority: Critical > Fix For: 3.0.0.Beta7 > > Attachments: 1-no-createEndpoint-permission.stacktrace, 2-no-createXnioWorker-permission.stacktrace, 3-no-addConnectionProvider-permission.stacktrace, 4-no-accessDeclaredMembers-permission.stractrace, 5-no-suppressAccessChecks-permission.stracktrace > > > # Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like > {noformat} > ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager > {noformat} > results in exception: > {noformat} > java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found > {noformat} > To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_: > {noformat} > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"), > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"), > new RemotingPermission("createEndpoint"), > new RuntimePermission("createXnioWorker"), > new RemotingPermission("addConnectionProvider"), > new RuntimePermission("modifyThread"), > new RuntimePermission("accessDeclaredMembers"), > new ReflectPermission("suppressAccessChecks") > {noformat} > which is very confusing. > Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-50) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-50: ---------------------------------------- Summary: Manual Testcases - Create and Run Key: HAWKULARQE-50 URL: https://issues.jboss.org/browse/HAWKULARQE-50 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Prachi Yadav -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-51) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-51: ---------------------------------------- Summary: Manual Testcases - Create and Run Key: HAWKULARQE-51 URL: https://issues.jboss.org/browse/HAWKULARQE-51 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Prachi Yadav -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8272) HttpServerExchange logout not happening after sessiontime out

by Ramesh khot (JIRA)

Ramesh khot created WFLY-8272: --------------------------------- Summary: HttpServerExchange logout not happening after sessiontime out Key: WFLY-8272 URL: https://issues.jboss.org/browse/WFLY-8272 Project: WildFly Issue Type: Bug Components: JSF, Security Affects Versions: 10.1.0.Final Reporter: Ramesh khot Assignee: Farah Juma I have an application deployed on wildfly-10.1.0.Final, using picketbox form based authentication integrated with SSO, we are using Jsf framework After ExternalContext.invalidateSession(); call UsernamePasswordLoginModule.logout() method is not triggered, which is used to happen in Jboss EAP 6.*, now I am calling request.logout() to flush the session data, which works for me After session time out invalidateSession is called but its not flushing session data, log says exchange null io.undertow.session trace log: *When request.logout():* 00:19:14,602 DEBUG [io.undertow.session] (default task-45) Invalidating session WUZTg0SSQXsbqgByND0Mpz1SMtcLExt7vGgrVr-E for exchange HttpServerExchange{ POST /plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.8,de-DE;q=0.6,de;q=0.4,en-GB;q=0.2], Accept-Encoding=[gzip, deflate], DNT=[1], User-Agent=[Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0; Firefox 45.7.0 - 11712-1502320053-1.34], Connection=[keep-alive], Cookie=[j_username=guest1; j_password=passguest1; JSESSIONID=WUZTg0SSQXsbqgByND0Mpz1SMtcLExt7vGgrVr-E.bmh1058602; JSESSIONIDSSO=PSz_b3ZYOtUYMPDC5_rdS-volKYXMH2j0pY-NLfe], Content-Type=[application/x-www-form-urlencoded], Content-Length=[116], Referer=[http://localhost:8090/plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml], Host=[localhost:8090]} response {Expires=[0], Cache-Control=[no-cache, no-store, must-revalidate], X-Powered-By=[Undertow/1], Server=[WildFly/10], Pragma=[no-cache]}} 00:19:18,864 DEBUG [io.undertow.request.security] (default task-45) Logging out user guest1 for HttpServerExchange{ POST /plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.8,de-DE;q=0.6,de;q=0.4,en-GB;q=0.2], Accept-Encoding=[gzip, deflate], DNT=[1], User-Agent=[Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0; Firefox 45.7.0 - 11712-1502320053-1.34], Connection=[keep-alive], Cookie=[j_username=guest1; j_password=passguest1; JSESSIONID=WUZTg0SSQXsbqgByND0Mpz1SMtcLExt7vGgrVr-E.bmh1058602; JSESSIONIDSSO=PSz_b3ZYOtUYMPDC5_rdS-volKYXMH2j0pY-NLfe], Content-Type=[application/x-www-form-urlencoded], Content-Length=[116], Referer=[http://localhost:8090/plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml], Host=[localhost:8090]} response {Expires=[0], Cache-Control=[no-cache, no-store, must-revalidate], X-Powered-By=[Undertow/1], Server=[WildFly/10], Pragma=[no-cache]}} 00:19:18,864 DEBUG [io.undertow.request.security] (default task-45) Logged out HttpServerExchange{ POST /plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.8,de-DE;q=0.6,de;q=0.4,en-GB;q=0.2], Accept-Encoding=[gzip, deflate], DNT=[1], User-Agent=[Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0; Firefox 45.7.0 - 11712-1502320053-1.34], Connection=[keep-alive], Cookie=[j_username=guest1; j_password=passguest1; JSESSIONID=WUZTg0SSQXsbqgByND0Mpz1SMtcLExt7vGgrVr-E.bmh1058602; JSESSIONIDSSO=PSz_b3ZYOtUYMPDC5_rdS-volKYXMH2j0pY-NLfe], Content-Type=[application/x-www-form-urlencoded], Content-Length=[116], Referer=[http://localhost:8090/plcdng_slim_dev/BootstrapUI/pages/protected/user/bootstrap.xhtml], Host=[localhost:8090]} response {Expires=[0], Cache-Control=[no-cache, no-store, must-revalidate], X-Powered-By=[Undertow/1], Server=[WildFly/10], Pragma=[no-cache]}} *After session time out:* Invalidating session H3Gy64JardrjwVMSxvKswFibxq136utoEnjZLdeG for exchange null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8270) Fix and improve Undertow* tests in elytron module

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8270?page=com.atlassian.jira.plugin.... ] Ondrej Kotek commented on WFLY-8270: ------------------------------------ Also ignored tests are blocked no more. Documentation should be improved. > Fix and improve Undertow* tests in elytron module > ------------------------------------------------- > > Key: WFLY-8270 > URL: https://issues.jboss.org/browse/WFLY-8270 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > > There are 4 tests in https://github.com/wildfly/wildfly/blob/master/testsuite/elytron/src/test... and each is creating client and making the call. > But the client is never closed. > I checked https://github.com/wildfly/wildfly/blob/master/testsuite/shared/src/main/... but it doesn't close the client either. > I think it makes sense to enhance those 4 tests with {{client.close();}} lines. > Changing Utils class can cause regressions when client is used for multiple calls. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8270) Fix and improve Undertow* tests in elytron module

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8270?page=com.atlassian.jira.plugin.... ] Ondrej Kotek updated WFLY-8270: ------------------------------- Summary: Fix and improve Undertow* tests in elytron module (was: UndertowSslSecurityDomainTestCase - close client to avoid resource leaks) > Fix and improve Undertow* tests in elytron module > ------------------------------------------------- > > Key: WFLY-8270 > URL: https://issues.jboss.org/browse/WFLY-8270 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > > There are 4 tests in https://github.com/wildfly/wildfly/blob/master/testsuite/elytron/src/test... and each is creating client and making the call. > But the client is never closed. > I checked https://github.com/wildfly/wildfly/blob/master/testsuite/shared/src/main/... but it doesn't close the client either. > I think it makes sense to enhance those 4 tests with {{client.close();}} lines. > Changing Utils class can cause regressions when client is used for multiple calls. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1351) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1351?page=com.atlassian.jira.plugi... ] Ivo Studensky reassigned WFCORE-1351: ------------------------------------- Assignee: Ivo Studensky (was: David Lloyd) > FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1351 > URL: https://issues.jboss.org/browse/WFCORE-1351 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Security > Reporter: Ondrej Kotek > Assignee: Ivo Studensky > Priority: Critical > Fix For: 3.0.0.Beta7 > > Attachments: 1-no-createEndpoint-permission.stacktrace, 2-no-createXnioWorker-permission.stacktrace, 3-no-addConnectionProvider-permission.stacktrace, 4-no-accessDeclaredMembers-permission.stractrace, 5-no-suppressAccessChecks-permission.stracktrace > > > # Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like > {noformat} > ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager > {noformat} > results in exception: > {noformat} > java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found > {noformat} > To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_: > {noformat} > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"), > new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"), > new RemotingPermission("createEndpoint"), > new RuntimePermission("createXnioWorker"), > new RemotingPermission("addConnectionProvider"), > new RuntimePermission("modifyThread"), > new RuntimePermission("accessDeclaredMembers"), > new ReflectPermission("suppressAccessChecks") > {noformat} > which is very confusing. > Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2161) UNICAST3: message delivery fails after disconnect-connect sequence

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2161?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2161: -------------------------------- Use JGroups-4.0.1-SNAPSHOT to test > UNICAST3: message delivery fails after disconnect-connect sequence > ------------------------------------------------------------------ > > Key: JGRP-2161 > URL: https://issues.jboss.org/browse/JGRP-2161 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Critical > Fix For: 4.1, 4.0.1 > > > When disconnecting and reconnecting a channel, unicast messages are not delivered. {{ConnectTest.testDisconnectConnectndMessageSending()}} reproduces the issue. -- 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