This procedure explains how to update the AzureAD Client Secret key used by SESAR for synchronization with Azure Active Directory.
Step 1: Prepare the new key in Azure
- In the Azure portal, open Azure Active Directory, then App registrations.
- Select the application used by SESAR.
- Go to Certificates & secrets.
- Create a New client secret.
- Copy the secret value immediately, that is the Value and not the Secret ID.
Warning: Azure only displays the Value once.
Step 2: Locate the next synchronization in the trace file
- Open the Trace_YYYY_M.log file, which contains the SESAR events. By default it is located in C:\Secure Exchanges inc\SESAR.
- Go to the end of the file and look for the line "Sync next lookup at YYYY-MM-DD 00:05:58", followed by the mention "You can stop the service before that time".
- Note the time shown: it is when the next synchronization will run.
Warning: Stop the service before that time, or wait until after the synchronization is complete, to avoid losing documents that are being synchronized.
Step 3: Stop the SESAR service
- On the SESAR server, open Services (services.msc).
- Locate the SESAR (Secure Exchanges Send And Receive) service.
- Right-click it and select Stop.
Note: The service must be stopped because SESAR only loads the configuration at startup.
Step 4: Update the configuration file and restart the service
- Once the service is stopped, replace the instance.json file with the unencrypted file you kept during the initial installation.
- Open the file and locate the AzureAD_Secret parameter.
- Replace the old value with the new Value copied from Azure.
- Save the file.
- Return to Services and start the SESAR service.
Warning: Make sure you do not add any spaces, unnecessary quotation marks or line breaks in the secret.
Note: Upon restart, the instance.json file is automatically encrypted again. Keep a copy of the updated unencrypted file in your secure vault.
Need help?
Our team is available to assist you. Write to us at support@secure-exchanges.com
Related Articles