Updating KeyManagerFactory algorithm to PKIX algorithm in java.security causes certificate to not be found/trusted. We found that ldapsdk logic is incompatible with PKIX-based key manager algorithm, likely due to certificate alias matching logic not accounting for PKIX-based alias prefixes (e.g. adding a debug in WrapperKeyManager.java:559 getPrivateKey() returns-> alias: 1.<cert-alias>). The prefix added by jvm PKIX algorithm causes alias to not match causing no trusted certificate exception to be thrown.
Is there a configuration to enable PKIX certificate handling by LdapSDK?