Page History

...

This wiki page has been hidden from the rest of the SHRINE documentation due to several problems and inaccuracies that require significant revision:

1. We should avoid using a real-life example of a third-party SSL/TLS provider, principally because different providers use different terminologies that may confuse remote sites.  I have also come across conflicting instructions on building a certificate chain (namely, that the order in which the certificates appear in such a file does and does not matter).  I have also seen in my actual tests that keytool has not consistently processed such concatenated files.  We should therefore ask the downstream sites to refer to their provider's instructions instead of presuming that a generic set of instructions is sufficient for all or even most use cases.
2. The original command to construct a PKCS12 file using the private key and its public certificate(s) does not actually define an alias for the entry in the file.  As a result, when the succeeding command is run to import the file into a keystore, the user is unaware that the default alias for the entry is "1" (numerical one), and therefore the import will fail.
3. The command to import the PKCS12 file into the keystore is likewise problematic in that it is evoking an alias where no such alias existed in the PKCS12 file (see previous problem).  As a result, the command as it stands in the overall sequence will fail when executed.

The solution to problems #2 and #3 is:

1. Require an explicit name for the alias in the PKCS12 file generation step, and then either
   1. Require a source alias and a destination alias when importing the PKCS12 file into the keystore, OR
   2. Omit all mentions of alias when importing, essentially turning the command into a keystore-to-keystore import.

This page should be rewritten before it is activated again.  I have made the recommendation above based on actual tests I conducted this afternoon (2020-May-15) using OpenJDK 11.0.7.

UPDATE (June 9, 2020):  This page has been rewritten to address the above concerns.  Unless there are additional, substantial changes requested, I am planning to release this page to the general SHRINE documentation later today.

By default, our recommendation for a typical ACT remote site is to have it submit a Certificate Signing Request (CSR) to the certificate authority (CA) of the ACT tier to which they are joining.  The CA will in turn generate a new certificate for the downstream site, and we will return that certificate, the hub certificate, and the CA certificate of the tier back to the downstream site.  The site will then import the certificates into their shrine keystore file, and configure their shrine.conf and server.xml to point to the alias entry in the keystore that corresponds to the site.

...