[JBoss JIRA] (WFCORE-2528) Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2528?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2528:
-------------------------------------
Description:
Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled.
was:
In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them..
Also re-enable the following test case: -
* org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite
> Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase
> ----------------------------------------------------------------------
>
> Key: WFCORE-2528
> URL: https://issues.jboss.org/browse/WFCORE-2528
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta9
>
>
> Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2528) Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2528:
----------------------------------------
Summary: Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase
Key: WFCORE-2528
URL: https://issues.jboss.org/browse/WFCORE-2528
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 3.0.0.Beta9
In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them..
Also re-enable the following test case: -
* org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1475) Item definition without allowed values and is collection set is ignored
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-1475:
-------------------------------------
Summary: Item definition without allowed values and is collection set is ignored
Key: DROOLS-1475
URL: https://issues.jboss.org/browse/DROOLS-1475
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.0.0.Beta7
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 7.0.0.Final
Simple type definitions without `allowed values` or `is collection` property set is ignored.
E.g.:
{code:xml}
<itemDefinition name="tSalary" id="_tSalary">
<typeRef>feel:number</typeRef>
</itemDefinition>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8255) New EJB Authentication tests (in AS TS) fail with Elytron profile
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-8255?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-8255:
-----------------------------
Fix Version/s: 11.0.0.Alpha1
> New EJB Authentication tests (in AS TS) fail with Elytron profile
> -----------------------------------------------------------------
>
> Key: WFLY-8255
> URL: https://issues.jboss.org/browse/WFLY-8255
> Project: WildFly
> Issue Type: Bug
> Components: Security, Test Suite
> Reporter: Josef Cacek
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> The newly introduced authentication tests ({{AuthenticationElytronTestCase}}, {{AuthenticationTestCase}}) in {{org.jboss.as.test.integration.ejb.security}} package fail when executed with Elytron AS TS profile.
> {noformat}
> cd testsuite/integration/basic
> mvn clean test -Dtest=org.jboss.as.test.integration.ejb.security.Authentication\* -Delytron
> ...
> Failed tests:
> AuthenticationElytronTestCase.testAuthenticatedCall:15->AbstractAuthenticationTestCase.testAuthenticatedCall:206 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication:15->AbstractAuthenticationTestCase.testAuthentication:136 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_BadPwd:148 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
> AuthenticationElytronTestCase.testAuthentication_TwoBeans:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans:161 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth:174 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:188 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
> AuthenticationElytronTestCase.testICIRSingle:15->AbstractAuthenticationTestCase.testICIRSingle:275 null
> AuthenticationElytronTestCase.testICIR_TwoBeans:15->AbstractAuthenticationTestCase.testICIR_TwoBeans:290 null
> AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth:312 null
> AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
> Tests in error:
> AuthenticationElytronTestCase.testAuthentication_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> Tests run: 38, Failures: 11, Errors: 16, Skipped: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers
by John Mazzitelli (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ]
John Mazzitelli commented on WFCORE-2526:
-----------------------------------------
Right, I am putting things in HOST_CONTROLLER_JAVA_OPTS in the .conf.
What you proposed sounds like a good solution for my use-case ("--server-excluded-properties")
> Domain mode passed unwanted sys props to spawned servers
> --------------------------------------------------------
>
> Key: WFCORE-2526
> URL: https://issues.jboss.org/browse/WFCORE-2526
> Project: WildFly Core
> Issue Type: Enhancement
> Reporter: John Mazzitelli
>
> This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props.
> I would say the solution should involve any properties, not just jboss.server.xxx properties.
> In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and
> "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up.
> But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent).
> See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month