/
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.

Related content

8.6. ConfiguraciĆ³n HTTPS
8.6. ConfiguraciĆ³n HTTPS
More like this
3.5.4. Certificate manager
3.5.4. Certificate manager
More like this
5. Certificate management
5. Certificate management
More like this
2.1.8.2. MW and eDocuments status map
2.1.8.2. MW and eDocuments status map
More like this
3. MW Communication
3. MW Communication
More like this
2.1.8.1. MW Customizing in SII
2.1.8.1. MW Customizing in SII
More like this

Avvale 2024