Authenticating HTTP users

For the HTTP application protocol, you can authenticate the user in the following ways:
  • You can use HTTP basic authentication.
  • You can use SSL client certificate authentication.
The authentication scheme is specified by the AUTHENTICATE and SSL attributes of the TCPIPSERVICE definition:
Authentication scheme AUTHENTICATE SSL Notes
HTTP with no authentication NO NO or YES  
HTTP with basic authentication BASIC NO, YES or CLIENTCERT  
HTTP with basic authentication AUTOMATIC NO, YES or CLIENTCERT If SSL(CLIENTCERT) is specified, and the client sends a certificate, then SSL client certificate authentication is used
HTTP with SSL client certificate authentication CERTIFICATE or AUTOREGISTER CLIENTCERT If the client does not send a certificate, the connection is not established
HTTP with SSL client certificate authentication AUTOMATIC CLIENTCERT If the client does not send a certificate, then basic authentication is used

Start of changeWhen CICS document templates and HFS files are delivered directly from a URIMAP definition, as a static response, basic authentication does not operate. End of change