API Authentication
This feature provides you the option to enable authentication on Unica Interact API calls. When it is enabled, Unica Interact RT checks if an incoming API request has a valid authentication token, if not, it authenticates it using the supplied username and password with Unica Platform or LDAP. The request is rejected if the token is not valid and username / password is not valid. Each token has a non-extendable lifetime of the Unica Interact session cache becomes timeout. The token is tied with the session-Id, which is provided during the startSession() API call. So all the other API calls validate this token before proceeding. This feature is disabled by default.
Third-party applications that intercept or modify network requests (e.g. load balancers, firewalls, proxies, request filters, antivirus, etc.) may interfere with Interact API / Deployment / Authentication requests.
Interact authentication may fail during deployment despite correct credentials, if third party applications (load balancers, firewalls, proxies, request filters, antivirus, etc.) are configured to intercept or rewrite messages on the network or app server. The result can be Interact deployment messages having their content length set to 0 by a third party, even though they have the correct authentication response content. Campaign has provided a workaround that reads the content regardless of the content-length tampering, thus restoring successful deployment authentication responses until the reason for the third-party tampering is found. This is not an Interact problem and you must contact Campaign support for the fix.