KB Article #73760
Bypass the default TLS profile as client SSL when using Gateway and Passport
When intitiating a transfer by using a tpmdea id (definition of the partner in Passport PM), the remote site build (.PHSE.00000x, .FTP.00000x, ...) will be based on the protocol remote site model (PHSE, FTP, ...) and will use a default TLS client profile if SSL/TLS is used.
Resolution
In order to be able to use different TLS profile with different settings as client:
- a new protocol remote site model need to be create by copying the protocol remote site model (PHSE, FTP, ...),
- on this new remote site, at 'Net Security' section by selecting 'TLS' as Network security option it will be possible to set a specific 'Security profile for outgoing connection'.
- by filling the parameter destination alias ('-da') into the model or peltrans request with this new protocol remote site model, the specific TLS profile settings will be take into account.