May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8724) Remove the AssumeTestGroupUtil and fix tests that use it

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-8724?page=com.atlassian.jira.plugin.... ] James Perkins moved WFCORE-2776 to WFLY-8724: --------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-8724 (was: WFCORE-2776) Component/s: Test Suite (was: Test Suite) > Remove the AssumeTestGroupUtil and fix tests that use it > -------------------------------------------------------- > > Key: WFLY-8724 > URL: https://issues.jboss.org/browse/WFLY-8724 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: James Perkins > > There is a {{AssumeTestGroupUtil}} utility in both WildFly and now WildFly Core. Tests that use this utility should be fixed to work with Elytron enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2776) Remove the AssumeTestGroupUtil and fix tests that use it

by James Perkins (JIRA)

James Perkins created WFCORE-2776: ------------------------------------- Summary: Remove the AssumeTestGroupUtil and fix tests that use it Key: WFCORE-2776 URL: https://issues.jboss.org/browse/WFCORE-2776 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: James Perkins There is a {{AssumeTestGroupUtil}} utility in both WildFly and now WildFly Core. Tests that use this utility should be fixed to work with Elytron enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2775) Remove the AssumeTestGroupUtil and fix tests that use it

by James Perkins (JIRA)

James Perkins created WFCORE-2775: ------------------------------------- Summary: Remove the AssumeTestGroupUtil and fix tests that use it Key: WFCORE-2775 URL: https://issues.jboss.org/browse/WFCORE-2775 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: James Perkins There is a {{AssumeTestGroupUtil}} utility in both WildFly and now WildFly Core. Tests that use this utility should be fixed to work with Elytron enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2392) Remoting EJB identity propagation does not work with Elytron

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2392?page=com.atlassian.jira.plugi... ] Josef Cacek resolved WFCORE-2392. --------------------------------- Fix Version/s: 3.0.0.Beta18 Resolution: Done > Remoting EJB identity propagation does not work with Elytron > ------------------------------------------------------------ > > Key: WFCORE-2392 > URL: https://issues.jboss.org/browse/WFCORE-2392 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: elytron-legacy-test-fails > Fix For: 3.0.0.Beta18 > > > Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. > Identity is unauthorized on server side. > *Remoting does not work because it is not implemented yet* - this issue created primary for tests ignore issue reference. > Often error message: > {code:java} > SaslException: Authentication failed: all available authentication mechanisms failed: > JBOSS-LOCAL-USER: Server rejected authentication > DIGEST-MD5: Server rejected authentication] > at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8720) Fix and unignore tests for switching identities in Elytron

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8720?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-8720: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/10025 > Fix and unignore tests for switching identities in Elytron > ---------------------------------------------------------- > > Key: WFLY-8720 > URL: https://issues.jboss.org/browse/WFLY-8720 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Critical > > Regression tests for WFCORE-2392 has to be unignored and updated (fixed) - {{org/wildfly/test/integration/elytron/ejb/AuthenticationTestCase.java}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8335) User should be informed when switching between JDBC and journal store in transactions subsystem

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-8335?page=com.atlassian.jira.plugin.... ] Claudio Miranda edited comment on WFLY-8335 at 5/8/17 2:41 PM: --------------------------------------------------------------- Hi Romain, I think there are some problems with the current implementation 1) the r-r-d doesn't set the alternatives correctly, the alternative of "use-jdbc-store" should contains "use-journal-store" and vice-versa. {code} "use-jdbc-store" => { "type" => BOOLEAN, "description" => "Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "requires" => ["jdbc-store-datasource"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" }, "use-journal-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" } {code} 2) when writing both "use-journal-store" and "use-jdbc-store" to true, the operation doesn't fail, it just sets the first one to true and the other to false. But it must fails. {code} batch [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-journal-store,value=true) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [domain@localhost:9990 / #] run-batch The batch executed successfully {code} I suggest to have a look at subsystem=elytron/dir-context=foo resource on how to handle the alternatives {code} [domain@localhost:9990 /] /profile=default/subsystem=elytron/dir-context=foo:add(url="ldap://foobar") [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /profile=default/subsystem=elytron/dir-context=foo:write-attribute(name=ssl-context,value="foo2") [domain@localhost:9990 / #] /profile=default/subsystem=elytron/dir-context=foo:write-attribute(name=authentication-context,value="bar2") [domain@localhost:9990 / #] run-batch The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0105: ssl-context is invalid in combination with authentication-context"}} {code} was (Author: claudio4j): Hi Romain, I think there are some problems with the current implementation 1) the r-r-d doesn't set the alternatives correctly, the alternative of "use-jdbc-store" should contains "use-journal-store" and vice-versa. {code} "use-jdbc-store" => { "type" => BOOLEAN, "description" => "Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "requires" => ["jdbc-store-datasource"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" }, "use-journal-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" } {code} 2) when writing both "use-journal-store" and "use-jdbc-store" to true, the operation doesn't fail, it just sets the first one to true and the other to false. But it must fails. {code} batch [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-journal-store,value=true) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [domain@localhost:9990 / #] run-batch The batch executed successfully {code} > User should be informed when switching between JDBC and journal store in transactions subsystem > ----------------------------------------------------------------------------------------------- > > Key: WFLY-8335 > URL: https://issues.jboss.org/browse/WFLY-8335 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Affects Versions: 10.1.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 11.0.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Precondition: 'Use journal store' or 'Use JDBC store' was previously set to true. > When enabling other type of store, user is not informed about the fact, that only one of those can be set and the previously enabled store is disabled and the new store is enabled without notification. User should be definitely informed about this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8335) User should be informed when switching between JDBC and journal store in transactions subsystem

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-8335?page=com.atlassian.jira.plugin.... ] Claudio Miranda commented on WFLY-8335: --------------------------------------- Hi Romain, I think there are some problems with the current implementation 1) the r-r-d doesn't set the alternatives correctly, the alternative of "use-jdbc-store" should contains "use-journal-store" and vice-versa. {code} "use-jdbc-store" => { "type" => BOOLEAN, "description" => "Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "requires" => ["jdbc-store-datasource"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" }, "use-journal-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => ["use-hornetq-store"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" } {code} 2) when writing both "use-journal-store" and "use-jdbc-store" to true, the operation doesn't fail, it just sets the first one to true and the other to false. But it must fails. {code} batch [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-journal-store,value=true) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [domain@localhost:9990 / #] run-batch The batch executed successfully {code} > User should be informed when switching between JDBC and journal store in transactions subsystem > ----------------------------------------------------------------------------------------------- > > Key: WFLY-8335 > URL: https://issues.jboss.org/browse/WFLY-8335 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Affects Versions: 10.1.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 11.0.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Precondition: 'Use journal store' or 'Use JDBC store' was previously set to true. > When enabling other type of store, user is not informed about the fact, that only one of those can be set and the previously enabled store is disabled and the new store is enabled without notification. User should be definitely informed about this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2746) Move elytron management security tests from full to core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2746?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-2746: ------------------------------ Description: Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 There are a number of aspects to this, for which I'll create subtasks. Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. org.jboss.as.test.integration.security.perimeter.* [2] org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- org.jboss.as.test.integration.security.credentialreference [2] (This is using h2 / datasources, so not moving). [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. [2] Currently using Arquillian. was: Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. There are a number of aspects to this, for which I'll create subtasks. Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. org.jboss.as.test.integration.security.perimeter.* [2] org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- org.jboss.as.test.integration.security.credentialreference [2] (This is using h2 / datasources, so not moving). [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. [2] Currently using Arquillian. > Move elytron management security tests from full to core > -------------------------------------------------------- > > Key: WFCORE-2746 > URL: https://issues.jboss.org/browse/WFCORE-2746 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security, Test Suite > Reporter: Brian Stansberry > > Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. > Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 > There are a number of aspects to this, for which I'll create subtasks. > Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. > org.jboss.as.test.integration.security.perimeter.* [2] > org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase > -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- > org.jboss.as.test.integration.security.credentialreference [2] (This is using h2 / datasources, so not moving). > [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. > [2] Currently using Arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8723) Move elytron management security tests from full to core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-8723?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-8723: ---------------------------- Description: This is the wildfly portion of https://issues.jboss.org/browse/WFCORE-2746 (was: This is the wildfly portion of ) > Move elytron management security tests from full to core > -------------------------------------------------------- > > Key: WFLY-8723 > URL: https://issues.jboss.org/browse/WFLY-8723 > Project: WildFly > Issue Type: Task > Reporter: Ken Wills > > This is the wildfly portion of https://issues.jboss.org/browse/WFCORE-2746 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8723) Move elytron management security tests from full to core

by Ken Wills (JIRA)

Ken Wills created WFLY-8723: ------------------------------- Summary: Move elytron management security tests from full to core Key: WFLY-8723 URL: https://issues.jboss.org/browse/WFLY-8723 Project: WildFly Issue Type: Task Reporter: Ken Wills Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 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 May 2017