#Keystore explorer entryname serial number#
#Keystore explorer entryname code#
#Keystore explorer entryname password#
#Keystore explorer entryname plus#

You can check the Certificate Authorities details in the MarkLogic Admin UI on port 8001 ( Configure > Security > Certificate Authorities) to ensure the Root CA certificate was added the certificate will be listed under the Organization Name that was specified when you created the certificate You should see an xs:unsignedLong is returned by the call to pki:insert-trusted-certificates if the certificate has been inserted successfully.

#Keystore explorer entryname code#

Specify the filename for the exported file in the example we are using /tmp/rootca.cer (this filename and path will be used later in this article to insert the trusted certificate into MarkLogic Server).Ĭlick Export to save the Root CA certificate to a fileĪnd click OK to dismiss the confirmation promptįrom the Query Console run the following xquery code against the Security Database: Select X.509 as the Export Format and check the PEM checkbox, if you have only a single Root CA certificate select Head Only otherwise select Entire Chain Right click on the Root CA entry in the KeyStore and select Export -> Export Certificate Chain Importing the Root Certificate Authority into MarkLogicīefore you can import the Root Certificate into MarkLogic you will first need to export it from the KeyStore Explorer tool in the correct format.

#Keystore explorer entryname password#

Verify that both the Key Usage and the Basic Constraints Certificate Extensions are now listed and click OKĬlick OK to complete the Root CA certificate generationĮnter a password to protect the private keyĪt this point the Root CA Certificate has been created With these selected, click OKĬlick the Green + button again and this time, select the Basic Constraints ExtensionĬheck the Subject is a CA box and click OK Select the Certificate Signing and CRL Sign attributes. You will see these are now listed under the Name field for the certificate.įor a Certificate Authority the Basic Constraints and Key Usage extensions are required.

#Keystore explorer entryname serial number#

Select RSA as the Algorithm and select a Key Size ( typically 2048)Īfter clicking on OK, most of the certificate details will already be pre-populated but you can change the Signature Algorithm, Validity and Serial Number as required.Ĭomplete the Certificate Subject details as necessary (in the example above, we're providing a Common Name, an Organization Unit and an Organization Name), then click OK to save these details. Right-click within the KeyStore workspace to open the context menu and select the Generate Key Pair option from the menu The first step is to create a valid Root Certificate Authority that will be used to sign all end-user or intermediate CA certificates Start KeyStore Explorer and select Create a new KeyStore or if you have already had a keystore you can use Open an existing KeyStore KeyStore Explorer can be downloaded from Getting Started Of course it would be possible for KSE to search the whole keystore for more certificates from the same chain and show them in the tree, but that would not match the real content of the TrustedCertificateEntry and it would confuse people even more.This Knowledgebase article demonstrates how you can use the KeyStore Explorer tools to generate a CA Root Certificate and end-user certificates for use with MarkLogic Server (for Application Servers which are SSL enabled) and for SSL based client authentication within your applications. You don't need to add the whole chain in a truststore, the root certificate is enough. This makes total sense if you think about the purpose of trusted certificates. Its issuer (my_ca) is in another TrustedCertificateEntry. If you click on a TrustedCertificateEntry, KSE shows the content of this entry, which is exactly one certificate. The two golden keys are the icon for a PrivateKeyEntry in KSE, whereas the red 'medal' is the icon for a TrustedCertificateEntry:

TrustedCertificateEntry = One single Certificate.

#Keystore explorer entryname plus#

PrivateKeyEntry = Private key plus certificate chain.

It is called a trusted certificate because the keystore owner trusts that the public key in the certificate indeed belongs to the identity identified by the subject (owner) of the certificate. This type of entry contains a single public key Certificate belonging to another party. It is also accompanied by a certificate chain for the corresponding public key. This type of entry holds a cryptographic PrivateKey, which is optionally stored in a protected format to prevent unauthorized access. To make it clear why this is as it is, let me first quote two definitions from the link to the KeyStore documentation above:

I understand your question very well and I understand why this is confusing for you.