cancel
Showing results for 
Search instead for 
Did you mean: 

TransportManagementService destination failing with 401

RaviRIyer
Explorer
0 Kudos
249

we do not seem to be able to get past a 401- un-Authorized error when checking a destination - in SAP BTP for configuring CTMS. I have re-created the Space and the destinations multiple times, SAP Ticket has been opened for it and configuration reviewed to no avail. 

ALL the 3 destinations that need oAuth ie "TransportManagementService", "ContentAssemblyService", "CloudIntegration" - fail the oAuth Check, when i do a transport check from BTP - Cloud Integration passes it, but the "TransportManagementService" Destination always fails with a bad credential error and hence fails to create a transport. 

Has anyone run into this and resolved it, would be nice if you could share specifics. 

With Regards

RI

View Entire Topic
SvenRullmn
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi RI,

In the case of "OAuth2ClientCredentials," the destination connection check in SAP BTP generally cannot verify whether a destination is configured with the correct authentication data. It only indicates whether the URL is reachable or not.

Besides, it seems that you still can't send transport requests to cTMS. There can be several reasons for this. A good first indication is the “Check Configuration” option in the Integration Suite. Within Integration Suite > Settings > Integrations > Transport > Transport Mode: "Transport Management Service" > "Check Confguration". The result should be

"{"results":[{"status":"SUCCESS","description":"Configuration check for CloudIntegration"},{"status":"SUCCESS","description":"Configuration check for TransportManagementService"}]}"

For instance if you missed to configure "sourceSystemId + <entry node> in your TransportManagementService destination, this checks returns:

{"results":[{"status":"SUCCESS","description":"Configuration check for CloudIntegration"},{"status":"ERROR","description":"Configuration check for TransportManagementService","error":{"uuid":"7fe35bb6-f9db-4b8e-8457-de99646ec4e7","internalMessage":"Property sourceSystemId or sourceSystemId.<xxx> is not found/configured properly."}}]}

We recently also published this tutorial about how to setup CPI content transports with CAS and cTMS. The steps described here might be helpful as well: https://developers.sap.com/tutorials/btp-transport-management-cpi-01-use-case.html

All the best,

Sven

RaviRIyer
Explorer
0 Kudos

@gauravi_shukla - Thank you so much for looking at this and replying,  i have gone through your blog, but if the destination to transport management from Content Agent is not working then you cannot transport from Content Agent as well. and solution fails. 

I have added Content Agent and CTMS - steps all done and re-done.  My issue matches with an exiting SAP Note -0003434418 -TMS check failed Destination configuration error in [TransportManagementService ] Bad credentials.

I have checked this note and re-done it several times with no difference. 

RaviRIyer_0-1744904200334.png

 

@Sven: Thank you, for looking and replying, i have gone through your blog as well, very useful. As for my issue - SAP team has checked and we are looking into why this destination is not working for us currently. As for the OAuth errors, all the blogs mention that we will get oAuth errors, but if that also gives an error like below and also the Content Agent cannot connect to the Transport management system, the whole solution as a whole fails with no real reason - i say real reason because i cannot see a reason for the failure in the transport logs or the CPI system logs., i am guessing SAP has more visibility into it and hopefully they will be able to identify the root cause here. 

{"results":[{"status":"SUCCESS","description":"Configuration check for CloudIntegration"},{"status":"ERROR","description":"Configuration check for TransportManagementService","error":{"uuid":"0b795ac5-5c03-44d6-bc8a-feabd3ea3731","internalMessage":"TMS check failed Destination configuration error in [TransportManagementService ] Bad credentials "}}]

my ticket is being looked at by the SAP Development team currently.

 

gauravi_shukla
Product and Topic Expert
Product and Topic Expert
0 Kudos

@RaviRIyerYou can check the destination configuration by referring to the help documentation link. It could be a case of misconfiguration or typo. You can check token URL client ID and secret once again. 
It should look something like this. 

Screenshot 2025-04-17 at 10.17.29 PM.png