Nov
19
2020
Allow PMode.Protocol.Address per PMode
<ul>
<li>Added the possibility to define a receiver URL (PMode.Protocol.Address) for each PMode set. These settings will overwrite the partners receipt URL if it is set. ENTSOG 3.5 states regarding this issue: "For a tuple of From/PartyId, From/Role, To/PartyId, To/Role, Service, Action values, organisations MAY agree to configure multiple processing modes differing on other P-Mode parameters such as certificates used, or the URL of endpoints.</li>
<li>Added the possibility to test connections and download and import remote certificates into the internal system</li>
<li>Added SNI (Server Name Indication) support to the connection test functionality - means if you are downloading a TLS certificate from a partner that is on a virtual host and requires SNI you will get the right/expected certificate</li>
<li>Added the possibility to delete all unused, expired key/certificate entries of the certificate manager with a single click. Therefor a new menu item has been added: "File-Delete all expired keys/certificates". Deleting these old entries is recommended because it makes no sense to perform cryptographic operations with expired certificates.</li>
<li>Added SNI (Server Name Indication) support to outbound HTTPS connections</li>
<li>[Windows only] Updated the underlaying JRE as there were problems with TLS 1.3. We recomment to update your JRE under non windows OS, too if you encounter TLS 1.3 problems.</li>
<li>[3rd party] Updated the underlaying crypto API to BC 167</li>
<li>[3rd party] Updated the apache HTTP components used for outbound connections from 4.5.6 to 4.5.13
<li>[3rd party] Updated the dark mode libs to flatlaf 0.43</li>
</ul>