[
https://issues.apache.org/jira/browse/CASSANDRA-17867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601931#comment-17601931
]
Josh McKenzie commented on CASSANDRA-17867:
-------------------------------------------
||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/1852]|
|JDK8
CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/294/workflows/b45ec1f8-3e6a-4cb6-a9e2-f07ecf3c2f64]|
|JDK11
CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/294/workflows/e0eb9b4a-7564-4d5b-a9d3-cda1455caae2]|
> Remove usage of deprecated javax certificate class
> --------------------------------------------------
>
> Key: CASSANDRA-17867
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17867
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
>
> When initially implemented, we used the older
> {{javax.security.cert.X509Certificate}} when initializing an
> {{IAuthenticator}} with certs - as nobody is yet using this interface, and
> there is a reasonable way to fix it to use the correct, non-deprecated cert
> classes, we should switch to the modern {{java.security.cert.Certificate}}
> class.
> The broader reasoning here is that consumers of this interface would have to
> jump through serialization/deserialization hoops on each authentication check
> to use the newer X509Certificate implementation, which has data on which we
> depend for our mTLS implementation, and in this case we can just cast them to
> the appropriate class.
> See
> https://docs.oracle.com/javase/9/docs/api/javax/security/cert/X509Certificate.html
> for further details
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
