4.2.2.33. AS4 Gateway IN

The AS4 gateway in exposes an AS4 endpoint that your partner's system can push messages into. Your partner will provide you with PMode (Processing Mode) information that will allow you to complete the gateway parameters. Note that if you are looking to interact over the Peppol AS4 network then you should create a Peppol gateway instead.

SERVICE NAME	The service name is part of the AS4 parameters that your partner will have requested or that you will have agreed upon (If left blank messages coming in with any service name will be accepted).
ACTION NAME	The action name is also part of the AS4 parameters that your partner will have requested or that you will have agreed upon. A service typically can support multiple actions. Again, if left blank all actions will be authorized.
REQUIRE ENCRYPTION*	In AS4 one can choose to encrypt messages in which case the receiver certificate will be used to decrypt the message.
REQUIRE SIGNATURE*	If checked, then messages that are not signed will be rejected. Signatures, when present, will be checked against the list of certificates you have trusted in your environment.
RECEIVER CERTIFICATE	This is the certificate that identifies you on the AS4 network. You likely have shared its public key with your partner and it will be used to decrypt incoming messages.
STRICT AS4 COMPLIANCE	If selected, messages which don't comply with AS4 preferred settings (such as payload character set or payload mime type explicitly) will be rejected.

 

The URL to your AS4 endpoint is displayed on the page properties.

 

Tips:

• When attempting to set up a connection for the first time, try to fill in as few fields as possible. Once you have specified a service or action name, all incoming traffic that doesn't match them will be rejected. Thus, in order to troubleshoot or initialize a setup, it is simpler to allow all incoming traffic and add restrictions once the basics of the connection are working.
• If you wish to be very strict on the authorized services and actions that a partner can contact you with, then you will have to create multiple gateways for these service and action combinations. This means you will have a different endpoint URL for each of these combinations. Alternatively, you can authorize all services and actions, and fail the messages that don't comply in your transformation by using the action and service metadata attached to the incoming message.