Replies: 7 comments 20 replies
-
|
Hello @uvula. What you have looks correct to me. For the tests did you migrate them to use For the stack traces, I think I need to know a bit more how |
Beta Was this translation helpful? Give feedback.
-
|
Hello jamezp, thanks for reply. About @Inject. Sure, from Jakarta.
About |
Beta Was this translation helpful? Give feedback.
-
|
Certificate is self-signed. With Java11 it is working, with Java17 not, but I assume the problem is the exceptions seen in Gradle debug. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, interesting. How do you setup the certificate in EAP? |
Beta Was this translation helpful? Give feedback.
-
|
Server: keystore/truststore loaded with *.p12 used by junit test. ` ` The junit test is using: ` ` Web.xml: ` ` With Java11 I see in server logging the mapping to the "RESTAccess" role. |
Beta Was this translation helpful? Give feedback.
-
|
Well shoot. This all looks correct. I'll have to see if I can create a reproducer. |
Beta Was this translation helpful? Give feedback.
-
|
Great. If I can help, let me know. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
~~Sorry for the delay, looking at this now. One thing I did notice is the protocol definition name looks wrong. It should be "Servlet 5.0". It wasn't changed to 6.0 because there just weren't any changes needed. ~~ Never min, this is wrong, there is a 6.0 :) Anyway, I'm going to try to create a reproducer now. |
Beta Was this translation helpful? Give feedback.
-
|
I don't seem to be able to reproduce this. One thing to check might be setting the <?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://jboss.org/schema/arquillian
https://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<defaultProtocol type="Servlet 6.0" />
<container qualifier="wildfly-managed" default="true">
<configuration>
<property name="allowConnectingToRunningServer">false</property>
<property name="jbossHome">${jboss.home}</property>
<property name="socketBindingName">https</property>
</configuration>
<protocol type="Servlet 6.0">
<property name="scheme">https</property>
<property name="host">127.0.0.1</property>
<property name="port">8443</property>
</protocol>
</container>
</arquillian>One thing to note, It looks like WildFly Arquillian overrides the URL injection which would normally be crated by the servlet protocol. The |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting. the The 403 forbidden does make sense though. Well, unless you're configuring the REST client with an If there is any way you could create a reproducer, that would be really helpful. I completely understand if you cannot though. That said, everything should work with SE 11, 17 and 21. We pass TCK's using Arquillian and WildFly Arquillian on 17 and 21. Plus WildFly and RESTEasy both test on all 3 SE versions as well. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a reproducer skeleton where I can start with? Gradle prefered. |
Beta Was this translation helpful? Give feedback.
-
|
And Monday I'm in vacation (one week), so it may take some time. |
Beta Was this translation helpful? Give feedback.
-
|
Hello jamezp, maybe you find a conclusion from my "reproducer" about the arquillian behavior. I started from scratch. a.) A module EJB with Arquillian is working (with Java17)
b.) added module for REST access. The test uses:
b1.)
b2.)
c.) Preparing WF with all the keystore/truststore/realms/security-domains using jboss-cli, as we started this discussion.
c1.)
c2.)
arquillian.xml is with b1, b2, c1, c2 located in the EJB module. |
Beta Was this translation helpful? Give feedback.
-
|
Hello jamezp, could you please be so kind and assist me once more? The following statement still applies: When I run EAP and Gradle tests with Java 11, all of my Arquillian tests pass. I have also set up the appropriate security domain in EAP so that only (test-) clients with the correct certificates I have found something new in the meantime. I.) I had a PC change, so my old server certificate from JBOSS EAP no longer matched (SAN = Subject Alternative Names). I have now changed this and observed the following improvement: Gradle+ Java17 with @RunAsClient exception: When I run Gradle with --debug and compare it with Java 11, I see the following major difference in the log; from this point on, it behaves quite differently under Java 17. Gradle + Java11 with @RunAsClient - no exception: With my limited knowledge and some research, I suspect that Thanks in advance for the help. |
Beta Was this translation helpful? Give feedback.
-
|
@uvula No problem and sorry for the delay on the other answer :) It's been on my TODO list, but I just have created a reproducer, I'm sorry for that. Are you using the junit-vintage dependency by chance? The |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, vacation. When I run .\gradlew.bat dependencies, I can NOT see any dependencies to junit-vintage. My gradle dependencies use e.g: or My code not using Junit4 dependencies, but I was looking for the class plus |
Beta Was this translation helpful? Give feedback.
-
|
BTW: when I pull wildfly-arquillian-* source code from Github and I want to run all the tests against a wildfly (e.g: WF33). Idea is: I make wildfly-arquillian-* running with WF33 running in my environment, and than I bring my tests here for my testings |
Beta Was this translation helpful? Give feedback.
-
|
Looking at the project, I might be wrong. It looks like it defaults to testing on 31.0.1.Final. However, you can override that on the command line by passing mvn clean install -Dversion.org.wildfly.full=33.0.1.FinalYou can download WildFly from https://wildfly.org/downloads. I'll try to do some more testing today as well. There seems to be a few different issues so I'm not clear on which issue you're currently seeing. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but I start to get crazy. But it guess the problem is also related to my Arquillian situation (with under Java17). Maybe you can follow my actually situation and make any conclusions about EAP8/Java17/Arquillian. PRE Jakarta: EAP 7.4.7 + Java11: Elytron is configurated as shown above in the discussion with all the security domain and SSLContext. I have two EARs (A + B). A is offering a REST Service and B is the client, using A. Moving to Jakakarta:
For me it looks like EAP is changing something in the "signature algorithms"? At least I see, the client certificate is not exchanged/requested from client when I have the EAP8_java17 with any Java17 client (EAR or standalone) I'm also confused about the TLS*? It looks like, TLSv1.3 is always ignored. I build with Arquillian/Gradle: in my comment from 09.August. As soon as the "server/client/arquillian" is in Java17-to-Java17, they can't negotiate the certificates (I guess).
|
Beta Was this translation helpful? Give feedback.
-
|
I think this whole time I've misunderstood this issue and I owe you a huge apology. I've been thinking you were referring to the management client, e.g. what Arquillian uses to deploy tests, etc. Think though you've been referring to a REST client in your test attempting to communicate with the deployment endpoints. I hope to have time to look at this today. |
Beta Was this translation helpful? Give feedback.
-
|
NO NO NO Again: EAP8 is setup with security domain + SSLContext from above. The tests are using https in arquillian.xml |
Beta Was this translation helpful? Give feedback.
-
|
Okay, sorry :) I'll create a reproducer, in Maven sorry, and share it so you can let me know if it's accurate for what you're doing. |
Beta Was this translation helpful? Give feedback.
-
I'm migrating from Java11/EAP7.4/JEE8/Gradle8.0.2 to Java11 &17 /EAP8/Jakarta EE 10.
The application (UI and REST API) itself is running within EAP8.
But I got some problems with my UnitTest and Arquillian.
I'm just a Arquillian user, I'm not so deep in the internals, maybe I use it the wrong way?
1.) all UnitTest wasn't running until I switched from wildfly-arquillian-container-managed:4.0.1 to
Before 5.1.0.Beta4, all the
@Injectobjects are still NULL. Executed within Arquillian an@Testmethods was called, but the@Injectobject are been null.With 5.1.0.Beta4 the injection is working now.
The test class is annotated with @ExtendWith(CertificateArquillianExtension.class). CertificateArquillianExtension is loading some certificate to SSLContext.
The JUnitTest uses RunAsClient
2.) the point 1.) was done with Java11, and all my tests are running now -> 5.1.0.Beta4.
I switched from Java11 to Java17 and the tests are failing again, I get a "jakarta.ws.rs.ForbiddenException: HTTP 403 Forbidden" exception.
But when I look to gradle with --debug I see a lot of:
There are a lot of excecption and it looks like a searching for other object like:
The actual dependencies, running with Java11 are:
Switching to Java17 will produce the above exceptions.
How do I run the tests?
a.) I have a shell, here the EAP8 is started, without any deployments
b.) From another shell, I launch "gradlew cleanTest test --tests "
Arquillian.xml
Any idea? Do I miss some dependencies?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions