From 2e3080b76f9a57d50e8875ef469be35de0b0be2c Mon Sep 17 00:00:00 2001 From: apalacheno Date: Fri, 14 Aug 2026 15:07:15 +0200 Subject: [PATCH] Update server_auth.md with updates on resolved intermediate certificate issues The bug that prevented MySQL from reading the intermediate certificate has been fixed in MySQL Server 8.0.30. --- docs/mysql/topics/server_auth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mysql/topics/server_auth.md b/docs/mysql/topics/server_auth.md index cf60ad4..b4f90dc 100644 --- a/docs/mysql/topics/server_auth.md +++ b/docs/mysql/topics/server_auth.md @@ -25,4 +25,4 @@ Restart your MySQL server for these changes to take effect. For additional security, step certificates are signed by an intermediate CA by default rather than the root CA. The intermediate certificate is bundled into your `{{ server_cert }}` file. -Unfortunately, MySQL has an [outstanding bug](https://bugs.mysql.com/bug.php?id=54158) that prevents it from being able to read the intermediate certificate out of `{{ server_cert }}`. So, when opening a connection from a MySQL client, we'll have to instead bundle that intermediate CA certificate together with the root CA certificate we saved previously (`{{ ca_cert }}`) and pass it into our client so that MySQL can read it and verify the server certificate that was signed by your CA's intermediate. This is covered in the Hello mTLS MySQL client docs. +MySQL had an [outstanding bug](https://bugs.mysql.com/bug.php?id=54158) (fixed in MySQL Server 8.0.30) that prevented it from being able to read the intermediate certificate out of `{{ server_cert }}`. So, if you are affected by this bug, when opening a connection from a MySQL client, you'd have to instead bundle that intermediate CA certificate together with the root CA certificate we saved previously (`{{ ca_cert }}`) and pass it into your client so that MySQL can read it and verify the server certificate that was signed by your CA's intermediate. This is covered in the Hello mTLS MySQL client docs.