In 2H-2023 SAP Introduced a limitation to only be able to setup SFTP server with port number 22.
We could configure & schedule a destination in Security Center > Destination with a port number different than 22.
it was confirmed by :
3148291 - Not able to use alternative ports for SFTP communication besides Port 22 (sap.com)
in B2311, it's still possible to select in Integration Center in Destination > Multiple Destinations > a destination with port different than 22.
NOW, in B2405, if you have your test instance refreshed with Production instance , you can no longer
reschedule your integration jobs to EXISTING DESTINATIONS in Security Center > Destination Settings (despite the precaution to have configure in PROD tenant the Destination Settings required for Test Tenant )
and Destination records in Security Center > Destination Settings with port number different than 22, then these destinations are no longer selectable.
SAP SUPPORT Don't want to recognise these as a regression.
I've opened a second ticket 533240/2024 to explain the situation comparing side by side what is possible in B2311 & B2405 release.
SAP Customer have to alter its architecture in test environment, introduce a new sftp server on port 22 or make an exception on a existing one to have connection on these port 22 (despite security through obscurity recommend to change these port to higher port than 22000 ), schedule a job to move the files to the company sftp server on a port different than 22.
ALL these in less than a month due to the release pushed on may 17th .
How can we exit these catch 22 situation ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.