-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
-
Server Security 2026-11-20
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Problem
On the macOS 15 distros (DEVPROD-45657 / SERVER-137597) every macOS variant fails ssl (1 test) and ssl_linear_macos (whole suite) because the hosts have no jstests x509 material:
- jstests/ssl/ssl_cert_selector_apple.js: security find-certificate -c "Trusted Kernel Test Server" -Z exits 44 (not found) — the Kernel Test certs are not in any keychain.
- jstests/ssl_linear/*: buildscripts/resmokeconfig/suites/ssl_linear_macos.yml passes sslCAFile: /opt/x509/macos-trusted-ca.pem; the file does not exist → "Unable to load PEM ... Failed opening file" for every test. On enterprise-macos amd64 this manifested as an idle timeout in repl_ssl_noca.js rather than a clean failure.
Evidence: https://spruce.corp.mongodb.com/version/6ad903bc0a71f20007041f5a (ssl, ssl_linear_macos on macos, macos-arm64, enterprise-macos, enterprise-macos-arm64). Green on macos-14 mainline 0f094cb6.
Cause
Host provisioning. buildhost-configuration disables the x509 role on macOS 15 (macos_jstests_x509: false) because Apple blocks scripted trust-settings writes (security add-trusted-cert → "no user interaction was possible") on macOS 15. The DevProd ticket linked from DEVPROD-45657 covers restoring the /opt/x509 file copy and attempting a non-trusted keychain import.
Ask for Server Security
- The /opt/x509 part is purely infra and should fix ssl_linear_macos with no test change. Nothing to do unless the suite still fails after the hosts are fixed.
- ssl_cert_selector_apple.js is the one test that depends on the keychain. The test comment already anticipates this case ("our trusted certificates are not installed on the machine's certificate keychain"). If DevProd cannot import the certs into a searchable keychain on macOS 15 without the trust bit, decide whether to (a) have the test skip when find-certificate returns 44 instead of asserting, or (b) tag it incompatible_with_macos (precedent: proxy-protocol jstests,
SERVER-135252). A one-line skip is probably the better option since the Secure Transport selector path would otherwise be untested on CI.
Downstream of the macOS 15 move; this will be a known red task on all 4 macOS variants until resolved.