openFT partners using openFT from version 8.1 onwards, support the authentication mechanism (see ). If the local system has a public key of the partner at its disposal, the partner’s identity is checked by cryptographic means.
For partner systems that do not work with authentication, inbound requests are checked with the aid of the instance identification, in order to ascertain whether the calling system has a valid entry in the partner list. openFT offers via extended sender checking the possibility of checking not only the instance identification, but also the transport address.
The extended sender checking can be globally enabled for openFT partners or just for specific partners:
globally, using
FTMODOPT ... PARTNER-CHECK=*TRANSPORT-ADDRESSonly for specific partners, using
FTADDPTN ... PARTNER-CHECK=*TRANSPORT-ADDRESS or
FTMODPTN ... PARTNER-CHECK=*TRANSPORT-ADDRESS
The global setting is valid for all partners with the value PARTNER-CHECK=*BY-FT-OPTIONS (default in the FTADDPTN).
In the case of FTAM and FTP partners, the sender check operates exclusively via the transport address. Consequently the "extended sender verification" attribute is ineffective for FTAM and FTP partners and is also not displayed.
Extended sender verification is of no relevance for dynamic partners because these are always identified via the transport address.
If the authentication check returns a negative result, the request is rejected.