Conversation level authentication

When a local TP attempts to allocate a conversation with a partner TP, the local LU sends an attach request to the partner LU, asking it to attach the partner TP. Under certain circumstances, the attach request can contain security information, which the partner LU can use to authenticate the local TP. This is known as conversation level authentication, or end user verification.

The following topics describe how IBM MQ provides support for conversation level authentication.

For more information about conversation level authentication, see Systems Network Architecture LU 6.2 Reference: Peer Protocols, SC31-6808. For information specific to z/OS, see z/OS MVS Planning: APPC/MVS Management, SA22-7599.

For more information about CPI-C, see Common Programming Interface Communications CPI-C Specification, SC31-6180. For more information about APPC/MVS TP Conversation Callable Services, see z/OS MVS Programming: Writing Transaction Programs for APPC/MVS, SA22-7621.

• Support for conversation level authentication on IBM i, UNIX, and Windows
  Use this topic to gain an overview of how conversation level authentication works on IBM i, UNIX, and Windows.
• Conversation level authentication and IBM MQ for z/OS
  Use this topic to gain an overview of how conversation level authentication works, on z/OS.

Parent topic: SNA LU 6.2 security services