/
2.1.8.3. HTTPS configuration

2.1.8.3. HTTPS configuration

Two-way communication with the middleware may require the use of the HTTPS secure transport protocol. In communication with the b+ cloud (FUSE), this configuration is mandatory. The tasks to be carried out for this are listed below:

1) Check in SMICM transaction that the HTTPS service exists (Menu option: Go to -> Services). If the HTTPS service does not appear, it needs to be configured.

2) Generate PSE SSL Client in transaction STRUST.

3) Import certificates from b+dgtal CAs into PSE SSL Client (Certificate List).

4) Generate PSE SSL Server in transaction STRUST.

5) Import certificates from b+dgtal CAs into PSE SSL Server (Certificate List).


Example of PSE generated with own signature and with list of certificates loaded:

 


6) It is necessary to export the public part of the PSE certificate (in case of own signature) and send it to the head of the middleware for import into this system. For that:

Select the certificate:

It will appear at the bottom for download:

In case of using a certificate issued by a CA, it will be necessary to send the certificates of the issuing root / intermediary CAs.

Avvale 2024