Closed Karm closed 5 months ago
/cc @cescoffier (rest-client), @geoand (rest-client), @sberyozkin (jwt,security)
This is probably related to #39563, where a context issue is also reported in the OT attempting to access the security identity, @michalvavrik FYI
Absolutely, thanks for reporting it. I have fix in progress and @brunobat is planning to remove the feature with #39648
Describe the bug
When I migrated a small test app from Jaeger to OpenTelemetry, a new exception has started to pop up in the log. Note that this is a tiny test app, mushing together client and server, initiating a REST Client call from within an already ongoing request. Perhaps that could be a part of the issue. I am fine refactoring the app, but it's not obvious to me if this is indeed an expected behavior. Despite "Security" keyword in the exception, I do not thing there is any immediate security implication at hand.
Expected behavior
There is no error in the log.
Actual behavior
How to Reproduce?
Then in a separate terminal, trivial, one client connection at a time:
You can run the OT collector too, but it doesn't seem to be necessary to see the issue:
The correct expected result of the call is:
Note that the call works fine, it's the exception in the log that is...unexpected.
Output of
uname -a
orver
Linux amd64, 5.14.0-425.el9.x86_64
Output of
java -version
21.0.1
Quarkus version or git rev
3.8.0, 3.8.3, 3.9.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /home/karm/Tools/apache-maven-3.9.6 Java version: 21.0.1-beta, vendor: Eclipse Adoptium, runtime: /var/X/JDKs/jdk-21.0.1+12 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.14.0-425.el9.x86_64", arch: "amd64", family: "unix"
Additional information
No response