Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# Defining Platform Server to the z/OS Security System

TIBCO MFT Platform Server for z/OS supports different security approaches to adapt to different security architecture you might implement in your environment.

The following security approaches are supported:

- The RACF Security Interface
- The Top Secret Security Interface
- The CA-ACF2 Security Interface

TIBCO MFT Platform Server for z/OS is a multi-user application. From a security perspective, TIBCO MFT Platform Server for z/OS must be defined to your security system as a multi-user address space, and all dataset access must be approved based on the individual user requesting the function. TIBCO MFT Platform Server for z/OS uses the z/OS Security Authorization Facility (SAF) to initialize and check security for each user at the time they initiate.

Because the Platform Server performs functions on behalf of multiple users, it must call the installed z/OS security system to create individual security environments (ACEEs) for each user and to verify that the correct password is entered for that user. All requests for resources, such as datasets, by that user are verified using that user's environment.

The type of security processing that the Platform Server performs depends on whether the local z/OS system initiates the request, in which case the Platform Server for z/OS acts as the initiator, or the Platform Server is processing a request that is started by a remote computer, in which case the Platform Server for z/OS acts as the responder.

- Initiator security processing: When a user invokes the client subtask to request that a file be transferred to or from a remote computer, the client software verifies if the user has access to the local dataset. When transmitting to the remote system, security information is transmitted to the remote node, including the remote user ID, the type of access, and an encrypted password.
- Responder security processing: When acting as a responder, the Platform Server extracts the necessary security information from the protocol data received from the remote system, including the name of the dataset, the user ID, the password, and the type of access. The Platform Server then uses the z/OS security manager to determine whether there is sufficient authority to perform the requested activity. TIBCO MFT Platform Server for z/OS and the z/OS server are subject to the same security checks as any other z/OS application. Therefore, TIBCO MFT Platform Server for z/OS must have a security profile, to have access privileges to any file that might be transferred or managed. Failing to define proper access can result in a 913 abend error.

The Platform Server identifies which user is trying to access the system depending on whether the file transfer is started by the local z/OS server or by a remote computer such as a Windows server.

- When the Platform Server started task is acting as an initiator, the Platform Server retrieves the initiator's user ID from z/OS control blocks, and places that user ID into the work queue dataspace of the Platform Server. The Platform Server does not support the user ID to run the request under the authority of anyone else.
- When the Platform Server started task is acting as a responder, the Platform Server receives the user ID and encrypted password over the data communications links, and then issues a `RACROUTE TYPE=VERIFY` command to ensure that the user ID is valid, and the user ID and password combination are a match.

Subtopics

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.