

- #CREATE SSL CERTIFICATE WINDOWS USING KEYSTORE EXPLORER INSTALL#
- #CREATE SSL CERTIFICATE WINDOWS USING KEYSTORE EXPLORER CODE#
The Export/Import method is the easiest and most popular option, especially for Windows servers. There are generally two methods used to deploy a single SSL certificate across multiple servers: The Export/Import method and the Issue/Reissue method. Or perhaps you purchase a multi-domain certificate, issued for many different domains, and you want to use it across multiple servers. If you buy a wildcard SSL certificate you may want to use that certificate across multiple servers that share the same base domain.
#CREATE SSL CERTIFICATE WINDOWS USING KEYSTORE EXPLORER INSTALL#
Why would you need to install on multiple servers? Summarizing: The Windows-My store holds certificates as well as private keys, both can be read from Java using the SunMSCAPI provider and can be used to sign digital documents."How do I install my SSL certificate on more than one server?" We get asked this question a lot. Signature sig = Signature.getInstance("SHA1withRSA", p) PrivateKey privKey = (PrivateKey) ks.getKey(alias, null) Ĭertificate cert = ks.getCertificate(alias) the following call requires SecurityPermission Note: When a security manager is installed,
#CREATE SSL CERTIFICATE WINDOWS USING KEYSTORE EXPLORER CODE#
There is a little code snippet as well, which seems to match your needs quite reasonably: KeyStore ks = KeyStore.getInstance("Windows-MY")

Maybe you want to take a look at Oracle's documentation on the SunMSCAPI provider, that can be used to access certificates and keys stored in the Windows-MY (Personal) and Windows-ROOT (Trusted Root Certification Authorities) stores. Java or Windows specific answers would be helpful but even just confirmation of the basic principles would be appreciated.

Unless I'm wrong, keytool will only ever generate a certificate type rather than an actual public/private key pair?Īny assistance or even affirmation would be greatly appreciated, apologies for the lack of clarity in the question but unfortunately this is all I have to work with at the moment. Check this certificate in WindowsMy store. Select “Place all certificates in the following store” radio button and click “Browse” button to Added it in windows Certificate store.Ĭ. Double click on “mykey.crt” and click on Install certificateī. Install the above certificate in windows keystore.Ī. Generate RSA key keytool -genkey -alias mykey -keyalg RSA -keystore my.jks -keysize 2048Įxport Certificate from the above keystore: keytool -export -alias mykey -file mykey.crt -keystore my.jks Here's some more evidence to support my case (communication from the client):Ĭreating Windows Key Store (Exporting from Java Keystore ) steps are here. Unfortunately there are a some communication difficulties so I'd like to make sure my reasoning is correct before proceeding any further. Am I incorrect, or will the Windows-MY keystore only ever contain a public certificate? I don't believe a private key would ever be embedded within one of these certificates. Now, my initial assumption is that what the client is requesting is simply not possible as this key store will only ever contain certificates, which can not be used for signing documents in any capacity. The client has requested the ability to use "Windows" keystores (more specifically, the Windows-MY keystore which relates to personal certificates as far as I can tell). This all appears fairly straightforward to me, however the change request has left me confused. The application is Java based, and makes use of Java Keystores (JKS) and uses the private key of the alias specified as a command line operation to digitally sign an input document. I've recently inherited a project with minimal documentation that performs digital signatures of documents and I've received a change request that has left me a little baffled.
