Migration to the new version of SESAR 2023-03-03

Migration to the new version of SESAR 2023-03-03

After gathering feedback from our clients, we agreed that updating SESAR could be a small challenge. Either replace the instance and modify the configuration file directly.
This is why since the last update of SESAR (23.02.2023) the instance is now in a separate file.

To migrate from the old version to the new version, follow these steps:

 1. Download the latest SESAR update
Go to the Secure Exchanges site to get the latest version of SESAR.

2.   Check the log file
Search for «next lookup at» in your logs.
If the delay is in the future, you can stop the service. However, if it is in the past, you must wait for the end of the synchronization.
 
3.   Stop Service


4.   Creating the Instance.json file
Rename the "sample_instance.json" file to "instance.json".

5.   Rename the file "SESAR.exe.config" to "old_SESAR.exe.config"


6.   Changing Values
Change the values of the "instance.json" file you have just renamed, with your values kept in a safe place.
Before (left values):                                                                                                                                                              After (right values):

  • Serial => Serial
  • APIUser = > APIUser
  • APIKey => APIKey
  • RefreshInterval => RefreshInterval
  • ConfigName => Name (note that the name property is outside the config property)
  • Mode => Mode (the value supposed to be Received)
  • KeyExchangesMode => KeyExchangesMode (the value supposed to be PKCS"
  • PathReceivedFolder =>PathReceivedFolder (your path folder where temp file will be downloaded)
  • PathStoreFolder => PathStoreFolder (the path where your data will be stored)
  • MaximumConcurentMessageDownload => MaximumConcurentMessageDownload (default value is 30)
  • PKCSComKey => PrivateComKey (note that property has change name. It's the private communication key)
  • PrivateFilesKey => PrivateFilesKey (the value is your private file key)
  • WebHookKey => WebHookKey
  • WebHookIv => WebHookIv
  • WebHook => WebHook (the url of your webhook
  • AzureAD_Secret => AzureAD_Secret
  • AzureAD_Client => AzureAD_ Client
  • AzureAD_Tenant => AzureAD_ Tenant
  • AzureAD_GroupName => AzureAD_ GroupName  (Before this Value was in the appSettings of the SESAR.exe.config file, now it is in the instance directly) 
Keep a copy of your.json instance in a safe place before launching the SESAR service, as the "instance.json" file will be encrypted and the "sample_instance.json" file will be overwritten with each update.
If you need to change values in your instance.json file, after following the steps to stop the service correctly, replace the contents of the instance.json file with the version you saved in a safe place and make your changes.

7.  Launch the SESAR service
Once your "instance.json" file is configured, you only need to launch the SESAR service and your file will then be encrypted by SESAR. The content should look like this:




    • Related Articles

    • SESAR update 2023.09.259 - october

      We are pleased to inform you of the availability of the latest update for SESAR (Secure Exchanges Send and Received). As a Windows service, SESAR plays a pivotal role in synchronizing exchanges made by your users, ensuring a complete copy of ...

    • How to configure SESAR with Azure Active Directory?

      1. Creating an app: Head to Azure Active Directory. Then, on the left bar click on “App registration” and click on “New registration”. Enter a name and then, under "Supported account types", check the first option "Single tenant". Finally, click on ...

    • 2022-09: Update - Signature Plugin: Our new signature features are here!

      Many of you asked us. Today, we are happy to announce it to you. During the last months, we worked hard to develop our signature plugin in order to better meet your needs and satisfy your expectations. As you suggested, we have included in our new ...

    • What are the SESAR configuration parameters?

      As SESAR works by “tenant”, an organization could have several “tenants”. So the configuration file is built so that the service is installed only once, but can retrieve information from all tenants So each SESAR is an instance that must be ...

    • 2022-10 : Update - New Improvements & New Packages

      In continuous development of our solution, our October update mainly includes improvements aimed at offering our users more flexibility and better ergonomics. To this end, we can identify two components: the first concerning improvements to ...