-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2.13] Perform security checks on inherited endpoints before payload deserialization in the RESTEasy Reactive #38992
[2.13] Perform security checks on inherited endpoints before payload deserialization in the RESTEasy Reactive #38992
Conversation
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
This comment has been minimized.
This comment has been minimized.
b0149d6
to
2eb4659
Compare
This comment has been minimized.
This comment has been minimized.
2eb4659
to
dd065b6
Compare
This comment has been minimized.
This comment has been minimized.
It looks like 2.13 CI is seriously unstable, sometimes even initial build fails. I can't reproduce the @jmartisk could you re-run the |
@michalvavrik I've triggered a rerun of the failed jobs now |
thanks @jmartisk , the test is now green. This PR has no relation to Gradle so I think it is ready for review. |
Status for workflow
|
Status | Name | Step | Failures | Logs | Raw logs | Build scan |
---|---|---|---|---|---|---|
✖ | Gradle Tests - JDK 11 | Build |
Failures | Logs | Raw logs | 🚧 |
✖ | Gradle Tests - JDK 11 Windows | Build |
Failures | Logs | Raw logs | 🚧 |
✔️ | Native Tests - Security3 | Failures | Logs | Raw logs | 🚧 |
Full information is available in the Build summary check run.
Failures
⚙️ Gradle Tests - JDK 11 #
- Failing: integration-tests/gradle
📦 integration-tests/gradle
✖ io.quarkus.gradle.BeanInTestSourcesTest.testBasicMultiModuleBuild
line 15
- History - More details - Source on GitHub
org.opentest4j.AssertionFailedError:
Expecting value to be true but was false
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at io.quarkus.gradle.BeanInTestSourcesTest.testBasicMultiModuleBuild(BeanInTestSourcesTest.java:15)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
✖ io.quarkus.gradle.ConditionalDependenciesTest.scenarioTwo
line 147
- History - More details - Source on GitHub
java.lang.AssertionError:
Expecting path:
/home/runner/work/quarkus/quarkus/integration-tests/gradle/target/classes/conditional-test-project/scenario-two/build/quarkus-app/lib/main/org.acme.ext-f-1.0-SNAPSHOT.jar
to exist (symbolic links were followed).
at io.quarkus.gradle.ConditionalDependenciesTest.scenarioTwo(ConditionalDependenciesTest.java:147)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
⚙️ Gradle Tests - JDK 11 Windows #
- Failing: integration-tests/gradle
📦 integration-tests/gradle
✖ io.quarkus.gradle.ConditionalDependenciesTest.scenarioTwo
line 147
- History - More details - Source on GitHub
java.lang.AssertionError:
Expecting path:
D:\a\quarkus\quarkus\integration-tests\gradle\target\classes\conditional-test-project\scenario-two\build\quarkus-app\lib\main\org.acme.ext-f-1.0-SNAPSHOT.jar
to exist (symbolic links were followed).
at io.quarkus.gradle.ConditionalDependenciesTest.scenarioTwo(ConditionalDependenciesTest.java:147)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
✖ io.quarkus.gradle.TestFixtureModuleTest.testTaskShouldUseTestFixtures
line 19
- History - More details - Source on GitHub
org.opentest4j.AssertionFailedError:
Expecting value to be true but was false
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at io.quarkus.gradle.TestFixtureModuleTest.testTaskShouldUseTestFixtures(TestFixtureModuleTest.java:19)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
⚙️ Native Tests - Security3 #
- Failing: integration-tests/keycloak-authorization
📦 integration-tests/keycloak-authorization
✖ io.quarkus.it.keycloak.PolicyEnforcerInGraalITCase.testHttpResponseFromExternalServiceAsClaim
- History - More details - Source on GitHub
org.opentest4j.AssertionFailedError: /api/permission/http-response-claim-protected ==> expected: <200> but was: <401>
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:560)
at io.quarkus.it.keycloak.PolicyEnforcerTest.assureGetPath(PolicyEnforcerTest.java:242)
at io.quarkus.it.keycloak.PolicyEnforcerTest.testHttpResponseFromExternalServiceAsClaim(PolicyEnforcerTest.java:174)
Thanks @michalvavrik , awesome job! @geoand could you give this a quick look, as you reviewed the original PR to main? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
\cc @aloubyansky |
@michalvavrik Can you please check the keycloak-authorization test ? I don't recall it being a flaky test. I've noticed it uses RestEasy Reactive |
@sberyozkin Please note that Also this PR has only relation on standard security annotation checks and there are no such annotations applied on the Only suspicious thing I can see in that log is long DNS request, but that is not related:
|
That may indeed cause 401 if the remote authorization check failed and agreed it would not be related to this PR |
backports #38832 with resolved conflicts