[#1307] Load the Docker administration certificate from a mounted Secret (#1308)
## Summary
- Load the administration keystore and PIN from `SECRET_VOLUME` on fresh
and reused volumes and during periodic refresh. Open the JKS or PKCS12
store with the default administration provider's loader and key manager
factory to check key recovery with the supplied PIN. Verify that the
selected `admin-cert` key can sign and matches its certificate. For
RSA-PSS, require the pair to sign and verify using a JSSE TLS scheme
with SHA-256, SHA-384, or SHA-512. Require the private key and
certificate to use the same algorithm and honor the certificate's Key
Usage and Extended Key Usage for TLS server authentication. Auxiliary
keys can use key agreement algorithms. A zero-byte PIN file is rejected,
and an empty first line supplies an empty password.
- Preserve the installed pair when validation fails or the
administration certificate nickname or key manager is customized.
Validate intact pending pairs and recheck the configuration and queued
changes immediately before installation. Move rejected pairs out of the
pending directory before cleanup. If the keystore has already moved,
finish installing its PIN on restart without the Secret mount, including
when configuration changes are queued.
- Document cert-manager 1.15+ with matching CRDs, a single-line ASCII
password for the JKS example, password rotation, the separate
`admin-truststore` password, and the BuildKit requirement. Show the
endpoint certificate's DNS SANs in the troubleshooting guide.
## Verification
- All 20 Docker administration TLS scenarios passed on both the standard
and Alpine images from the previous round with the updated validator.
The local runs used `-XX:ActiveProcessorCount=2` and a shorter
health-check interval. The tests check the served certificate serial on
port 4444 and confirm that `dsconfig` succeeds with CA trust and
hostname verification.
- An RSA-PSS pair with different private- and public-key minimum salt
lengths replaces the installed certificate and completes CA- and
hostname-verified TLS 1.2 and 1.3. A pair that matches no JSSE TLS
scheme leaves the installed certificate in service during mounted Secret
updates and intact pending recovery.
- The installed certificate stays usable when an `admin-cert` key that
cannot sign arrives through the Secret mount or is recovered from an
intact pending directory. The tests also preserve the installed
certificate when a mounted pair has a certificate that disallows digital
signatures, a client-only certificate, or mismatched RSA and RSA-PSS key
types. The auxiliary X25519 scenario still succeeds, and PIN-only
recovery succeeds with a queued configuration change and no Secret
mount.
- The validator and the JKS fixture generator compiled with `javac
--release 11`. The Maven Docker package contains the updated validator
source and entrypoint. Shell syntax and `git diff --check` passed.
Fixes #1307