TransportManagementService destination failing with 401

[RaviRIyer]

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

[Ryan-Crosby]

Pretty sure that is the normal behavior for the destination check in BTP.

[gauravi_shukla]

Could you assign the SAP ticket to this component "BC-CP-LCM-CAS"?

[gauravi_shukla]

---

@RaviRIyer wrote:

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

---

You can try to use SAP Content Agent service UI (offered with overall contract of SAP BTP with no additional cost). Here is the link to blog post that you can refer to: https://community.sap.com/t5/technology-blogs-by-sap/transport-selected-artefact-to-cloud-transport-...

In SAP Content Agent UI, you can navigate to "Cloud Transport Management" page and view the connection status, follow the documentation in case of any misconfiguration, select the source node for creating the transport request.

[RaviRIyer · Accepted solution]

Ok i was able to fix this, i had to manually re-create the entire destination, every time you edit the destination the client ID value seems different, so to be consistent, anytime you make any change to the destination, "even if you click edit and save" with no changes  ..points to remember

1. Enter the client ID - again - copy from Service Key JSON.

2. Enter the client Secret value - again - copy from Service Key JSON. 

3. Token Service User and Token Service Password are NOT required, even if they are entered it will NOT be used until the "Use mTLS for token retrieval" is checked. 

Hope this helps. 

Regards

Ravi