[Red Hat JIRA] (WFCORE-4217) ManagementAuthenticationUsersTestCase fails with Elytron profile
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFCORE-4217?page=com.atlassian.jira.plug... ]
Martin Choma updated WFCORE-4217:
---------------------------------
Steps to Reproduce:
{code}
cd testsuite/standalone/
mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
{code}
was:
cd testsuite/standalone/
mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
> ManagementAuthenticationUsersTestCase fails with Elytron profile
> ----------------------------------------------------------------
>
> Key: WFCORE-4217
> URL: https://issues.redhat.com/browse/WFCORE-4217
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
> {noformat}
> {noformat}
> [INFO] Running null
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in null
> [ERROR] Failure when constructing test Time elapsed: 0.003 s <<< FAILURE!
> java.lang.AssertionError:
> WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.executeForSuccess(ManagementAuthenticationUsersServerSetupTask.java:113)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.setup(ManagementAuthenticationUsersServerSetupTask.java:65)
> at org.wildfly.core.testrunner.WildflyTestRunner.runSetupTasks(WildflyTestRunner.java:121)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:107)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-5121) Requires click Build button to update column field type
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5121?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-5121:
----------------------------------------
As of today, sanity check for 7.47.0.Final, the behaviour is still the same as originally reported.
New proof, step 1:
!Screenshot 2020-12-02 at 16.40.35.png|thumbnail!
result:
!Screenshot 2020-12-02 at 16.40.47.png|thumbnail!
> Requires click Build button to update column field type
> -------------------------------------------------------
>
> Key: DROOLS-5121
> URL: https://issues.redhat.com/browse/DROOLS-5121
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Matteo Mortari
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: ScesimRequiresBuildButtonToUpdateColumn.mov, Screenshot 2020-12-02 at 16.40.35.png, Screenshot 2020-12-02 at 16.40.47.png
>
>
> as attached
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (ELY-2049) Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
by Boris Unckel (Jira)
[ https://issues.redhat.com/browse/ELY-2049?page=com.atlassian.jira.plugin.... ]
Boris Unckel updated ELY-2049:
------------------------------
Description:
The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
Examples:
[Undertow|https://issues.redhat.com/browse/UNDERTOW-1815]
[java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
line 2048
The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
Current code:
{code:java}
public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
ProtectionDomain deniedDomain = null;
if (domains != null) for (ProtectionDomain domain : domains) {
if (! domain.implies(permission)) {
final CodeSource codeSource = domain.getCodeSource();
final ClassLoader classLoader = domain.getClassLoader();
final Principal[] principals = domain.getPrincipals();
if (principals == null || principals.length == 0) {
access.accessCheckFailed(permission, codeSource, classLoader);
} else {
access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
}
if (deniedDomain == null && ! LOG_ONLY) {
deniedDomain = domain;
}
}
}
return deniedDomain;
}
{code}
was:
The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
Example:
[java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
line 2048
The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
Current code:
{code:java}
public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
ProtectionDomain deniedDomain = null;
if (domains != null) for (ProtectionDomain domain : domains) {
if (! domain.implies(permission)) {
final CodeSource codeSource = domain.getCodeSource();
final ClassLoader classLoader = domain.getClassLoader();
final Principal[] principals = domain.getPrincipals();
if (principals == null || principals.length == 0) {
access.accessCheckFailed(permission, codeSource, classLoader);
} else {
access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
}
if (deniedDomain == null && ! LOG_ONLY) {
deniedDomain = domain;
}
}
}
return deniedDomain;
}
{code}
> Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
> -----------------------------------------------------------------------
>
> Key: ELY-2049
> URL: https://issues.redhat.com/browse/ELY-2049
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Security Manager
> Affects Versions: 1.13.2.Final
> Reporter: Boris Unckel
> Priority: Major
>
> The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
> Examples:
> [Undertow|https://issues.redhat.com/browse/UNDERTOW-1815]
> [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
> line 2048
> The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
> Current code:
> {code:java}
> public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
> ProtectionDomain deniedDomain = null;
> if (domains != null) for (ProtectionDomain domain : domains) {
> if (! domain.implies(permission)) {
> final CodeSource codeSource = domain.getCodeSource();
> final ClassLoader classLoader = domain.getClassLoader();
> final Principal[] principals = domain.getPrincipals();
> if (principals == null || principals.length == 0) {
> access.accessCheckFailed(permission, codeSource, classLoader);
> } else {
> access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
> }
> if (deniedDomain == null && ! LOG_ONLY) {
> deniedDomain = domain;
> }
> }
> }
> return deniedDomain;
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFCORE-4217) ManagementAuthenticationUsersTestCase fails with Elytron profile
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFCORE-4217?page=com.atlassian.jira.plug... ]
Martin Choma updated WFCORE-4217:
---------------------------------
Steps to Reproduce:
cd testsuite/standalone/
mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
> ManagementAuthenticationUsersTestCase fails with Elytron profile
> ----------------------------------------------------------------
>
> Key: WFCORE-4217
> URL: https://issues.redhat.com/browse/WFCORE-4217
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
> {noformat}
> {noformat}
> [INFO] Running null
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in null
> [ERROR] Failure when constructing test Time elapsed: 0.003 s <<< FAILURE!
> java.lang.AssertionError:
> WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.executeForSuccess(ManagementAuthenticationUsersServerSetupTask.java:113)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.setup(ManagementAuthenticationUsersServerSetupTask.java:65)
> at org.wildfly.core.testrunner.WildflyTestRunner.runSetupTasks(WildflyTestRunner.java:121)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:107)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (ELY-2049) Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
by Boris Unckel (Jira)
[ https://issues.redhat.com/browse/ELY-2049?page=com.atlassian.jira.plugin.... ]
Boris Unckel updated ELY-2049:
------------------------------
Description:
The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
Examples:
[Undertow|https://issues.redhat.com/browse/UNDERTOW-1815]
[WildFly 1|https://issues.redhat.com/browse/WFLY-14072]
[WildFly 1a, including Stacktrace|https://issues.redhat.com/browse/WFLY-14039]
[java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
line 2048
The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
Current code:
{code:java}
public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
ProtectionDomain deniedDomain = null;
if (domains != null) for (ProtectionDomain domain : domains) {
if (! domain.implies(permission)) {
final CodeSource codeSource = domain.getCodeSource();
final ClassLoader classLoader = domain.getClassLoader();
final Principal[] principals = domain.getPrincipals();
if (principals == null || principals.length == 0) {
access.accessCheckFailed(permission, codeSource, classLoader);
} else {
access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
}
if (deniedDomain == null && ! LOG_ONLY) {
deniedDomain = domain;
}
}
}
return deniedDomain;
}
{code}
was:
The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
Examples:
[Undertow|https://issues.redhat.com/browse/UNDERTOW-1815]
[java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
line 2048
The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
Current code:
{code:java}
public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
ProtectionDomain deniedDomain = null;
if (domains != null) for (ProtectionDomain domain : domains) {
if (! domain.implies(permission)) {
final CodeSource codeSource = domain.getCodeSource();
final ClassLoader classLoader = domain.getClassLoader();
final Principal[] principals = domain.getPrincipals();
if (principals == null || principals.length == 0) {
access.accessCheckFailed(permission, codeSource, classLoader);
} else {
access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
}
if (deniedDomain == null && ! LOG_ONLY) {
deniedDomain = domain;
}
}
}
return deniedDomain;
}
{code}
> Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial
> -----------------------------------------------------------------------
>
> Key: ELY-2049
> URL: https://issues.redhat.com/browse/ELY-2049
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Security Manager
> Affects Versions: 1.13.2.Final
> Reporter: Boris Unckel
> Priority: Major
>
> The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions.
> Examples:
> [Undertow|https://issues.redhat.com/browse/UNDERTOW-1815]
> [WildFly 1|https://issues.redhat.com/browse/WFLY-14072]
> [WildFly 1a, including Stacktrace|https://issues.redhat.com/browse/WFLY-14039]
> [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...]
> line 2048
> The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs.
> Current code:
> {code:java}
> public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) {
> ProtectionDomain deniedDomain = null;
> if (domains != null) for (ProtectionDomain domain : domains) {
> if (! domain.implies(permission)) {
> final CodeSource codeSource = domain.getCodeSource();
> final ClassLoader classLoader = domain.getClassLoader();
> final Principal[] principals = domain.getPrincipals();
> if (principals == null || principals.length == 0) {
> access.accessCheckFailed(permission, codeSource, classLoader);
> } else {
> access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals));
> }
> if (deniedDomain == null && ! LOG_ONLY) {
> deniedDomain = domain;
> }
> }
> }
> return deniedDomain;
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFCORE-4217) ManagementAuthenticationUsersTestCase fails with Elytron profile
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFCORE-4217?page=com.atlassian.jira.plug... ]
Martin Choma commented on WFCORE-4217:
--------------------------------------
I still see the issue in master following reproducer.
{code}
[ERROR] Failures:
[ERROR] WFLYCTL0216: Management resource '[
("core-service" => "management"),
("security-realm" => "ManagementRealm")
]' not found
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
{code}
> ManagementAuthenticationUsersTestCase fails with Elytron profile
> ----------------------------------------------------------------
>
> Key: WFCORE-4217
> URL: https://issues.redhat.com/browse/WFCORE-4217
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase
> {noformat}
> {noformat}
> [INFO] Running null
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in null
> [ERROR] Failure when constructing test Time elapsed: 0.003 s <<< FAILURE!
> java.lang.AssertionError:
> WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.executeForSuccess(ManagementAuthenticationUsersServerSetupTask.java:113)
> at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.setup(ManagementAuthenticationUsersServerSetupTask.java:65)
> at org.wildfly.core.testrunner.WildflyTestRunner.runSetupTasks(WildflyTestRunner.java:121)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:107)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]' not found
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months