[NET-384] KeyManagerUtils - the KeyManager is not efficient

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Assignee: Unassigned
• Reporter: Sebb
• Created: 21/Mar/11 14:55
• Updated: 04/Jun/11 19:26
• Resolved: 21/Mar/11 17:43

Description

The clientKey manager performs some of the work that could be done as part of creating the key store.

Since the manager is potentially called many times, it would be better to move the setup processing to the creation of the keystore.

This requires creating a sub-class of KeyStore, which might as well be a private class created by createClientKeyManager()

The calling sequence would then be:

KeyManager km = KeyManagerUtils.createClientKeyManager(
    "JKS", "/path/to/privatekeystore.jks", "storepassword", "privatekeyalias", "keypassword");
FTPSClient cl = new FTPSClient();
cl.setKeyManager(km);

For JKS stores with a single entry and keypassword == storepassword this would simplify to:

KeyManager km = KeyManagerUtils.createClientKeyManager("/path/to/privatekeystore.jks", "storepassword");
FTPSClient cl = new FTPSClient();
cl.setKeyManager(km);