fix(auth): enforce client certificates and configured CRL checks

[mbuckton]

Summary

• preserve required/wanted client-certificate policy on generated SSL engines
• wrap the configured X.509 trust manager so normal CA validation and CRL checking both execute
• fail the handshake when revocation status cannot be established
• retain the existing public CRL trust-manager constructor with safe default CA validation
• add regression tests for client-auth precedence and CRL composition

Companion change

Server transport/configuration fixes: Maps-Messaging/mapsmessaging_server#2162

Verification

Focused tests were added under src/test/java/io/mapsmessaging/security/ssl. This managed environment cannot run the Maven build because the repository and Maven dependency cache are not available locally; the repository currently exposes no PR workflow/status check.

SECURITY: TLS client authentication and CRL enforcement

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4497a581-d02f-4299-9a73-d82c449a5dff

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}