Authentication

The Web Engagement History REST API supports the Basic HTTP authentication (see http://www.ietf.org/rfc/rfc2617.txt) scheme.

Important

HTTP authentication should be used with Secured HTTP communication (HTTPS).

Configuration

The REST API security is configured in the [security] section of the Web Engagement Server application. The following configuration options are mandatory to enable authentication:

• auth-scheme
• user-id
• password

Note: If authentication is used, every REST API client must support that authentication type and the clients must know the authentication credentials. You must configure authentication for Interaction Workspace and if your Engagement strategies use the REST interface, you must also add your authentication credentials. See Configuring Authentication in the Deployment Guide for details.

Basic Authentication

This authentication scheme passes unencrypted credentials, so it is unsafe unless you use a secured connection (HTTPS).