Updates (changes or additions) to this document are listed as follows.
Changes to the document made: November 8, 2013:
Modified Move your legacy certificate folder structure (Niagara 3.8)to clarify that copying the legacy file structure forward applies only if upgrading to NiagaraAX 3.8 from a previous version.
Modified Create a folder structureto accommodate both version 3.7 and 3.8 users.
Changes based on NiagaraAX 3.8 made: November 5, 2013
Rewrote the answer to the question about the upgrade path to explain that the security folder is automatically copied forward when NiagaraAX is updated. See Frequently-asked questions.
Added a topic to suggest that legacy users should cut and paste their current certificate folder structure to the new certManagement folder. See Move your legacy certificate folder structure (Niagara 3.8).
Modified Create a folder structure to explain that opening Certificate Management for the first time automatically creates the certManagement folder.
Modified the certificate creation and signing graphics in Certificate creation to illustrate the certManagement folder. Added introductory sentences to several of the items in the ordered lists that follow the certificate creation illustrations.
Changes to 3.7u1 made: August 16, 2013
Made general editorial changes throughout the book, for example, removed “decrypt” and “decryption” based on the assumption that the word “encrypt/encryption” covers both directions.
Rewrote the answer to “Does using multiple keys slow performance?” inFrequently-asked questions.
Combined all best practices into one section of the introductory chapter. See NiagaraAX SSL best practices.
Rewrote the answer to the comment/question, “Our company already has signed certificates. Can they be used on our JACEs?” See NiagaraAX SSL best practices.
Rewrote the answer to the question that begins, “Is there an upgrade path for SSL security...”. This is the last paragraph before NiagaraAX SSL best practices.
Added two sentences to the fifth bullet, rewrote the fourth bullet, and rewrote the last bullet from the end of Security considerations.
Changed the note following the last bullet in Security considerations to a caution and rewrote the final sentence.
Added a sentence that begins, “Before you begin...” in the introduction to Install SSL module.
Added a qualifying phrase at the beginning of the section Check for SSL license.
Rewrote the discussion following step 3 in Enable the Web Service connection.
Added a note to explain that when Https Enabled is set to true, Foxs Enabled must also be set to true. See Confirm the Fox Service connection
Added the paragraph beginning “Ideally, you want to set...” as part of the discussion following step 2 in Confirm the Fox Service connection
Created a new section, Temporarily approve the self-signed certificates.
Reworked Configure outgoing email.
ReworkedUpgrade from crypto.jar.
Resized all the drawings in About SSL—Alice, Bob, Cathy and Bart and About NiagaraAX SSL so that they will look better in the help system.
Added an explanation of “man-in-the-middle attack” to When things go wrong.
Reworked Keys.
Reworked portions of Signing a certificate with a private key.
Made significant changes to the Figure 18 in the section titled NiagaraAX’s client/server architecture, including adding numbers to the illustration so that it is easier to identify the relationships being called out.
Reworked Workbench certificate signing, including changing an error in the illustration.
Combined very similar information into About the SSL Toolset and reworked the wording to contain all the unique information from the similar sections.
Added a new question and answer pair to document a login error. See Fix error conditions.
Reworked Reset or replace a JACE securely.
Rewrote the definition of CA Certificate in SSL Toolset terminology.
Rewrote the descriptions of these properties: Fox Enabled, Foxs Enabled, Foxs only and added a note describing how each are used. See Fox Service configuration properties. Did the same for Http Enabled, Https Enabled, and Https only. See Web Service configuration properties.
3.7 Update 1 (3.7u1): May 31, 2013.
Rewrote a number of procedures in “Set up Workbench and stations for SSL” on page 2-1 and “Create certificates” on page 3-1, including replacing screen captures.
Confirmed that daemonCrypto and cryptoCore have been removed as required modules leaving only a single module: platCrypto. See “Prerequisites” on page 2-1 and “Upgrade from crypto.jar” on page 2-11.
Removed any recommendation to delete the old crypto.jar from the modules folder. This file is deleted automatically. See “Upgrade from crypto.jar” on page 2-11.
Updated the section titled “Enable clients and configure them for the correct port” on page 2-9 with an additional step to temporarily approve the unsecured host until one or more certificates are configured. Added a paragraph explaining this use of the Allowed Hosts list to About Allowed Hosts.
Added the step to “Enable SSL” on page 2-4 to right-click and select the action to disconnect all Fox sessions so that the station can reconnect using Foxs. Also added a question/answer pair about this issue to Fix error conditions.
Added to this Document Change Log a reference to “3.7 Update 1 (3.7u1)” to clarify that this is a modified version of a release that is already in the field.
Performed other document maintenance tasks.
Updated: February 21, 2013
Noted in several areas that starting in the NiagaraAX 3.7 Update 1 release (3.7u1 or 3.7.104) or later, only the platCrypto module is required to be installed in a Hotspot JACE for SSL support. In the initial 3.7 release (3.7.44), modules cryptoCore and daemonCore were also required. Affected sections are Prerequisites, Install SSL module, and Upgrade from crypto.jar.
More specific details were also given about JACE platforms that do not support the “SSL Toolset” described in this document: the JACE-2 series and JACE-4/5 series controllers—which use the IBM J9 VM instead of the required Hotspot VM. Even if upgraded to NiagaraAX 3.7 or later, this group of JACE-2/4/5 controllers must continue to use the station-based CryptoService for SSL. Affected sections were Prerequisites and Upgrade from crypto.jar.
Initial publication: August 30, 2012.
Copyright © 2000-2016 Tridium Inc. All rights reserved.