For an inbound two-way synchronous exchange, you can configure such connection
settings as the security, and receipt and error message delivery settings.
Before you begin
Ensure that you have selected the required AS4 receiver.
About this task
This task involves specifying security settings and receipt
and error message delivery settings for the inbound two-way synchronous
request.
To configure inbound connection settings, complete the following procedure:
Procedure
- In the Inbound Push Request section
of the AS4 inbound two-way synchronous exchange profile, click Configure in
the Connection Settings section.
- On the Configure Connection Settings screen,
complete the following steps:
Field |
Description |
Authorization
|
To enable user authorization, select the Enable
User Authorization check box and select the user authorization
mode. The available user authorization modes are:
- User exit - A user exit is used to authorize
a user.
- Select list of allowed user subjects -
Select the trading partner user subjects who can use the exchange
profile. To add the user subjects click Add Credential.
Tip: You can add a user subject on the Organization Credentials
(Security > Organization Credentials) page.
|
Encryption
|
If you selected an encryption enabled conformance policy for the exchange profile,
you must select an encryption certificate in the Security section.
You can select an existing encryption certificate, or click Add Certificate
to upload a new certificate. Only RSA X.509 certificates are supported in AS4 Microservice
|
Signature
|
Specify signature settings to authenticate
the trading partner. Select the option by which you want to authenticate
the trading partner system (sender):
- Use embedded certificate and authenticate using global
trust store - Select the option to use the embedded certificate
and authenticate using the global truststore.
- Verify using the configured certificate -
Select a specific trading partner certificate that can be used for
authenticating the sender.
Tip: In a two-way synchronous exchange pattern, errors are
sent over the same HTTP or HTTPS connection. A separate HTTP destination
is not required.
|