cancel
Showing results for 
Search instead for 
Did you mean: 

How to update FNE Publisher keys in FNO Cloud and ALM On prem and keep the same Identity

How to update FNE Publisher keys in FNO Cloud and ALM On prem and keep the same Identity

Summary

How to update FNE Publisher Keys in FNO Cloud and ALM on Prem and keep the same Identity

Synopsis

If a customer changes the FNE publisher keys (add new platform support) in FNOC (ALM/LLM) or FNO (ALM) and needs to keep the same identity, they will need to follow the instructions below to update their existing Identities. If they are in a testing phase it much easier to generate a new identity in FNOC using the UI and download that new identity to the FNE Clients.

Discussion

If the customer changes the publisher keys and has FNOC (ALM/LLM) we need to update the publisher keys for them since there is no UI for that (enter a Jira and Andy (DBA) will do it for you).

If the customer has FNO (ALM) the publisher keys will be automatically updated by following the steps below.

If they want to keep the same identity name they will need to update the existing Identity.

  1. Download the existing identity files from FNOOD
    1. Copy these files to some back-up location in case you want to revert
    2. Download all 3 binary files from FNOOD and save them in your work directory (you don?t need the C or Java files)
    3. In FNOOD, navigate to the Identity you want to update
    4. Create some work directory
  2. Start pubidutil (which you can find in your FNE /bin/tools directory)
    1. Pubidutil has updated your keys in the work directory (check time stamp of the files)
    2. Click submit
    3. Change the publisher keys
    4. pubidutil should show you the old publisher keys as well as the identity name and key algorithm and strength
    5. point pubidutil to the bin files you just downloaded to your work directory
  3. Go back to FNOC and upload the new IdentityBackOffice.bin
    1. navigate to the Identity you want to update
    2. Click update
    3. Click Browse
    4. Find the updated IdentityBackOffice.bin and click submit
    5. Acknowledge the warning
    6. The application will upload your identity file with the new publisher keys
  4. Verify
    1. Download the Client Identity in either C or Java flavor and open the file in a text editor. In the header you should see the new publisher keys
    2. Test that a client that had the old identity file can still communicate with the back office
    3. Test that a client with the new identity file can communicate with the back office

Labels (1)
Was this article helpful? Yes No
No ratings