-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
why does Quarkus return a deprecated X509Certificate? #12371
Comments
In which context, does Quarkus return a deprecated |
For instance, making a filter using Reactive Routes:
From Do you need futher information? I'm using 1.8.1.Final of |
@serrodcal it is off-topic, but do you do an access token binding to the client cert check ? We've been thinking to do it for a while for quarkus-oidc bearer tokens (#4482), may be also worth trying for smallrye-jwt... |
Our problem is building to native, because the only way to convert to the non deprecated X509Certificate (which is needed to be able to use a library to validate the Access Token) is using the serialization. I don't know if there is other way to do that. |
A small reproducer project would help also |
I can't share the project because it belong to my company, but I'll try create a small reproducer project as you mentioned as soon as possible :). |
Description
I'm not sure where to put this question. I hope I am in the right place.
The question is, why does Quarkus return a deprecated X509Certificate?
When I want to get the certificate from the request, I get a
javax.security.cert.X509Certificate
instead ofjava.security.cert.X509Certificate
.Implementation ideas
I was wondering if with Vert.x v4, this issue will be fixed or not. But, Quarkus/Vert.x should work with no deprecated objects. Mainly, trying to build in native with filters, a serialization is needed as given below:
This is needed because to be able to use libraries to validate a JWT token I need the
java.security.cert.X509Certificate
, but in native I got an error in runtime because the serialization doesn't work.The text was updated successfully, but these errors were encountered: