CICS as an HTTP client: authentication and identification

When you make an HTTP client request through CICS®, a server or proxy might require you to perform basic authentication, proxy authentication, or SSL client certificate authentication. Basic authentication and proxy authentication are carried out by your user application. A client certificate can be supplied using a URIMAP definition.

Your client application might be asked to authenticate itself in the following ways:

Some servers might ask you to provide other types of authentication or identification. If you are unable to provide acceptable authentication or identification to a server, your request will be rejected. For basic authentication or proxy authentication, the status code used when a server rejects your request is the same as the status code for the challenge (401 for a server or 407 for a proxy). If you respond to a challenge but then receive a further response with one of these status codes, the authorization information you used is not valid.