SymXchange Implementation Blueprints

Create a Key configuration and certificate to be used for your Banno SymXchange instance:

1. Log in to System Web Console.
2. Navigate to Key Management > Key Store Configuration.
3. Click the New Configuration button.
4. At the Name prompt, enter a name for the new key configuration.
   • Ex: BANNO_SYMxxx (where xxx is the SYM number)
5. At the Description prompt, enter a description for the new key configuration.
6. At the Host SYM prompt, select the SYM under which SymXchange runs.
7. Click Save.
   • The new key configuration now appears in the key store configuration list.
8. From the list, select the new key configuration.
   
9. Click the Key Stores tab.
10. Click the Open Key Store icon next to the key store.
11. Click Create Key.
12. At the Alias prompt, enter an alias.
    • Ex: banno_symxxx (where xxx is the SYM number)
13. At the Days of Validity prompt, type 3650.
14. At the Key Size prompt, select 2048 bits.
15. At the Common Name (CN) prompt, enter a name.
    • Ex: symx.<CU_Name>.local
      
16. Remaining fields are not required but can be filled in if desired.
17. Click Create.
    • The new key alias now appears in the key store.

1. Log in to the System Web Console.
2. In the System Web Console window, select Key Management from the menu list.
   • The Key Store Configuration List pane appears.
3. In the Configuration Name column, select the key configuration created for Banno.
4. Select the Key Stores tab, and then click the Open Key Store icon.
   • The Key Management pane appears.
5. Click the Export icon.
   • The Export Key dialog box appears.
6. Leave the Private Key Password prompt blank.
7. At the File Name prompt, type a relevant name.
8. At the File Format prompt, click the drop-down arrow, and then select PEM.
9. Click the Export button to save the .pem file to your local drive.
10. Upload the certificate to the Banno Implementation/Update jSource case.
    • Important: You must upload the file to a secure internal access point. Send the file using a secured method. Do not use email.

1. Log in to System Web Console.
2. Navigate to Key Management > Key Store Configuration.
3. From the list, click the Banno key configuration created previously.
4. Click the Key Stores tab.
5. Click the Open Trust Store (folder) icon to the right of the key store.
6. Click Import.
7. Click Choose, and then navigate to the file containing the Banno-provided certificate.
8. Click Upload.
   • A dialog box appears with the public key in .pem format.
9. At the Alias prompt, enter service_banno.
   • The alias must be service_banno.
   • The alias should be all lowercase without spaces.
10. Click Import.
    • The public certificate now appears as part of the trust store.

1. Log in to System Web Console.
2. Navigate to Key Management > Key Store Configuration.
3. Click the New Configuration button.
4. At the Name prompt, enter a name for the new key configuration.
   • Ex: JHProxyService_SYMxxx (where xxx is the SYM number)
5. At the Description prompt, enter a description for the new key configuration.
6. At the Host SYM prompt, select the SYM under which SymXchange runs.
7. Click Save.
   • The new key configuration now appears in the key store configuration list.
8. From the list, select the new key configuration.
   
9. Click the Key Stores tab.
10. Click the Open Key Store icon next to the key store.
11. Click Create Key.
12. At the Alias prompt, enter an alias.
    • Ex: jhproxyservice_symxxx (where xxx is the SYM number)
13. At the Days of Validity prompt, type 3650.
14. At the Key Size prompt, select 2048 bits.
15. At the Common Name (CN) prompt, enter a name.
    • Ex: symx.<CU_Name>.local
      
16. Remaining fields are not required but can be filled in if desired.
17. Click Create.
    • The new key alias now appears in the key store.

1. Log in to the System Web Console.
2. In the System Web Console window, select Key Management from the menu list and click on Key Store Configuration.
   • The Key Store Configuration List pane appears.
3. In the Configuration Name column, select the key configuration created for JHProxyService.
4. Select the Key Stores tab, and then click the Open Key Store icon.
   • The Key Management pane appears.
5. Click the Export icon.
   • The Export Key dialog box appears.
6. Leave the Private Key Password prompt blank.
7. At the File Name prompt, type a relevant name.
8. At the File Format prompt, click the drop-down arrow, and then select PEM.
9. Click the Export button to save the .pem file to your local drive.
10. Upload the certificate to the JH ISO Wires Implementation/Update jSource case.
    • Important: You must upload the file to a secure internal access point. Send the file using a secured method. Do not use email.

1. Log in to System Web Console.
2. Navigate to Key Management > Key Store Configuration.
3. From the list, click the JHProxyService key configuration created previously.
4. Click the Key Stores tab.
5. Click the Open Key Store (folder) icon to the right of the key store.
6. Click Create Key.
7. At the Alias prompt, type ecaas_id_provider. The alias must be ecaas_id_provider. ID cannot be changed to the sym number.
8. At the Days of Validity prompt, type 3650.
9. At the Key Size prompt, select 2048 bits.
10. At the Common Name (CN) prompt, type ECAAS.
11. Leave any remaining fields empty.
12. Click Create.
13. Click the button in the Trust column for the ecaas_id_provider entry.
    • The following message appears: Trust key result: Successfully copied certificate.

1. Log in to System Web Console.
2. Navigate to Key Management > Key Store Configuration.
3. From the list, click the JHProxyService key configuration created previously.
4. Click the Key Stores tab.
5. Click the Open Trust Store (folder) icon to the right of the key store.
6. Click Import.
7. Click Choose, and then navigate to the file containing the Banno-provided certificate.
8. Click Upload.
   • A dialog box appears with the public key in .pem format.
9. At the Alias prompt, enter service_banno.
   • The alias must be service_banno.
   • The alias should be all lowercase without spaces.
10. Click Import.
    • The public certificate now appears as part of the trust store.