 |
 |
||||||||
|
 |
||||||||
|
|
 |
New Features and Updates for APPX Router
Last Update: 11/17/01
4. APPX Mainframe Enhancements
==============================
Sessions established by the APPX Router now have additional status
information available. This includes the IP address of the originating
station, the encryption mode and preference tag in effect, the user ID,
inserted APPX data and the data block from the remote encryption database
or database DLL. This data is available with APPX v3.36.
For non-router established sessions, most extended data will be null,
except for APPX/TCP sessions direct to CICS, which will have an IP address
specified. SNA LU2 and LU6.2 sessions will include the LU name of the
originating node.
The additional data is retrieved after a successful APPX connect via the
APPX PPX-GET-EXTENDED-CONNECT-DATA function. This function returns a
"PPE-CONTROL-BLOCK" structure which is described in Appendix F,
"APPX/Mainframe Encryption/Extended Connect Info Block." This block
contains information about the node connecting to the mainframe, and if
an indirect (APPX Router) connection is involved, data from the Router,
including authentication information and information about the encryption
mode in effect, is included.
Programming notes:
- While no currently available mainframe APPX directly supports
encryption, applications should not depend on the
PPE-AUTHENTICATION-DATA being available only if the PPE-INDIRECT-LINK
flag is set.
- If both Router and non-Router based connections to the mainframe
APPX application are allowed, some care must be taken to ensure that
the authentication data is valid. It is technically possible to fake
the portion of the APPX datastream that contains the authentication
data from the APPX Router, if a non-APPX Router intermediated reliable
link APPX connection is established to the host. If the application
allows such connections, provisions should be made to validate the
source of the authentication data. If external authentication data
is presented to the mainframe APPX, the PPE-INDIRECT-LINK flag will
be set (if authentication, in a future version, is handled by the
mainframe APPX, that flag will not be set). If the PPE-INDIRECT-LINK
flag is set, the application should check the source of the data
by inspecting the PPE-LINK-TYPE, PPE-LU-NAME, PPE-SNA-NET-NAME and
PPE-IP-ADDRESS fields. Authentication data should only be accepted
from a trusted source.
| << Previous Page | Next Page >> |
