-
Notifications
You must be signed in to change notification settings - Fork 566
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
Helidon 4.0.2 with JWT Auth fails with UnsupportedCharsetException: UTF-32LE #8195
Comments
For posterity, this is failing, I guess, in your environment, correct? (For completeness, both Helidon 4.0.1 and 4.0.2 use Parsson 1.1.5, I guess.) That smells to me like not all character sets are available at runtime and probably something like |
If I change my
|
Confirmed |
* #8195 JSON unicode detection workaround for eclipse-ee4j/parsson/issues/121
Environment Details
Helidon Version: 4.0.2
Helidon MP
JDK version:
openjdk 21.0.1 2023-10-17
OpenJDK Runtime Environment GraalVM CE 21.0.1+12.1 (build 21.0.1+12-jvmci-23.1-b19)
OpenJDK 64-Bit Server VM GraalVM CE 21.0.1+12.1 (build 21.0.1+12-jvmci-23.1-b19, mixed mode, sharing)
OS: macOS
Problem Description
I'm trying to upgrade my Java REST API example to use Helidon 4.0.2 and GraalVM CE 21.0.1.
oktadev/auth0-java-rest-api-examples#58
The last time I ran this example, I used Helidon 4.0.1 and GraalVM CE 21. I don't recall having any issues.
After upgrading, I'm getting the following error when running as a native image and trying to access the
/hello
endpoint with an access token.If I use
helidon dev
, everything works fine.I figured if I reverted to GraalVM 21 (
sdk install java 21-graalce
) and Helidon 4.0.1, it'd fix the problem. However, it still persists after downgrading, so I'm quite confused.Steps to reproduce
Create an Auth0 tenant and copy your domain into
src/main/resources/META-INF/microprofile-config.properties
.Create an access token using the Auth0 CLI:
Set the returned access token as a
TOKEN
variable:In a new terminal window, start the Helidon app:
Access it with the token:
You'll see the following stacktrace:
The text was updated successfully, but these errors were encountered: