HTTP Policy Configuration- Advanced

Use this tab to specify the type of user authentication to use for inbound access requests. For Certificate Authentication and User Authentication through External Authentication, you must have installed and configured Secure External Authentication Server. HTTP Policy Configuration - Advanced fields are defined in the following table.

Field Name

Description

External Authentication Profile

External Authentication Profile identifies the name of the certificate validation definition you defined in the Secure External Authentication Server. You must enable certificate validation before you can provide a profile.

User Authentication Type

User authentication to enable. To enable single sign-on, select Application Authentication for browser based clients and basic authentication for non-browser based clients.

Through External Authentication

Turn on User Authentication through External Authentication to send an incoming user ID and password to Secure External Authentication Server for validation.

External Authentication Profile

If you enabled user authentication through Secure External Authentication Server, identify the certificate authentication profile you defined in Secure External Authentication Server.
Note: This field is only used for reference purposes when using SAML external IdP. Since SEAS supports only one IdP, no separate profile need to be created in SEAS.

Through Local User Store

Validates the user ID and password of the inbound node using information defined in the user store. You must add the user to the user store to successfully use this method.

Internal User ID

User ID and password used to attach to the server in the secure environment. For the user ID and password presented to the Sterling B2B Integrator server to successfully access the server, a user definition must be defined at the Sterling B2B Integrator server. User mapping options include:
  • User ID/Password passed through from client—Uses the user ID and password supplied by the inbound node to connect to the server in the secure zone. To successfully connect to the server, the user ID and password must be defined in the user store at the server.
  • User ID/Password From Secure External Authentication Server—Uses a user ID and password from Secure External Authentication Server to connect to the server. To successfully connect using this option, the user ID and password must be defined in the LDAP database.
  • User ID/Password from netmap—Uses the user ID and password defined in the netmap to connect to the outbound server. To successfully connect using this option, define the user ID and password to use in the outbound node definition.
  • SSO token from Secure External Authentication Server—Uses a token from Secure External Authentication Server to authenticate the user to the server.

Block Common Exploit Strings

Enable this option to scan inbound URI queries for any of the defined strings. If a match is found, the request is rejected and the connection is closed. Default blocked strings include: --, |, ', \, <?, \u0000. To modify the common exploits that are blocked, modify the strings.