Summary

This article explains how to update FlexNet Embedded publisher keys in FlexNet Operations Cloud (ALM or LLM) and ALM On Premises and keep the same identity.

Synopsis

If a customer changes the FlexNet Embedded publisher keys (add new platform support) in FlexNet Operations Cloud (ALM/LLM) or ALM On Premises 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 is much easier to generate a new identity in FlexNet Operations Cloud using the user interface and download that new identity to the FlexNet Embedded Clients.

Discussion

If the customer changes the publisher keys and has FlexNet Operations Cloud (ALM/LLM), Revenera Support needs to request the publisher keys be updated in FlexNet Operations Cloud.

If the customer has FlexNet Operations On Premises (ALM), the publisher keys will be automatically updated by following the steps below.

If the customer wants to keep the same identity name, they will need to update the existing identity.

1. Download the existing identity files from FlexNet Operations Cloud.
   
   1. Create a work directory.
   2. In FlexNet Operations Cloud, navigate to the identity you want to update.
   3. Download all three binary files from FlexNet Operations Cloud and save them in your work directory. (You do not need the C or Java files.)
   4. Copy these files to a back-up location in case you want to revert.
2. Start pubidutil (which you can find in your FlexNet Embedded /bin/tools directory).
   1. Point pubidutil to the bin files you just downloaded to your work directory.
   2. pubidutil should show you the old publisher keys as well as the identity name and key algorithm and strength.
   3. Change the publisher keys.
   4. Click Submit.
   5. pubidutil updates your keys in the work directory. (Check the time stamp of the files.)
3. Go back to FlexNet Operations Cloud 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 file 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.