You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Bryan G. Behrenshausen" <se...@apache.org> on 2026/03/02 19:29:55 UTC
Proposed article: Navigating the Public Certificate Authority Client Authentication EKU Sunset with Apache Geode
Hello team,
In May, public certificate authorities will stop including the Client
Authentication Extended Key Usage (EKU) in public TLS certificates. This major
change could have significant implications for users of Apache Geode.
Jinwoo Hwang, Principal Software Developer at SAS and release manager of
Apache Geode 2.0, has composed an article outlining three viable strategies
for mitigating the effects of this change. We would like to propose publishing
it on the ASF blog.
I will attach to this email a plain-text version of the piece for your
consideration. I will also connect with members of the Marketing and Publicity
PMC to provide formatted versions of the article, as well as the necessary
graphics files.
Sincerely,
Bryan Behrenshausen
Re: Proposed article: Navigating the Public Certificate Authority Client Authentication EKU Sunset with Apache Geode
Posted by Melissa Logan <me...@constantia.io>.
Hi Bryan, thanks for reaching out. The way that this is currently written
would make more sense as a post on the Geode blog because it's aimed at
Geode users.
However, public CAs sunsetting clientAuth EKU potentially touches any
Apache project using mTLS with public certificates. To make it more
relevant for the main ASF blog, would you open to updating the overall
perspective to encompass the broader industry impact, and impact on other
ASF projects (e.g. Kafka, Cassandra etc)? Insights from those projects
would be valuable to add.