on 2024 Jun 25 9:22 AM
Hello experts,
We've configured TMS to transport iflows between out two environments, but we're stuck with the end phase of the process. When we want to import the component to the destination account we have the next error:
Exception during start of deployment for deploy type 'SLP_CTS': Error during client creation: Unauthorized
The corresponding target destination is created according with the documentation, the url is
https://deploy-service.cfapps.<your DC>.hana.ondemand.com/slprot/<org name on DEV subaccount>/<DEV space name>/slp
The user informed in the destination has the space developer role in the space we want to transport.
Could you give us any clue about the problem?
Thanks in advance.
Request clarification before answering.
Hello Lance,
We still continue stuck with this issue. We've tested against two diferent account. The first one is our operative subaccount, and we tested with a trial account too, but with same result. When we want to import, unauthorized.
Transport request '<request_id>' (id: 223): Exception during start of deployment for deploy type 'SLP_CTS': Error during client creation: Unauthorized
When we want to check the destination against the target subaccount we always get the next result
Failure reason: "Could not check at the moment. Please try again later"
We have followed the steps detailed in the next blog - https://sapzero2hero.com/2022/06/15/sap-cpi-transport-package-by-using-transport-management-service-...
We continue trying to resolve the issue. If we have any advance I will tell you.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fernando,
I was able to get it to work today. Below are my observations
1) User Account had multiple SIDs
My CTMS instance was deploying to CloudFoundry using a destination that was configured with OAuthPassword auth method with a test user account that was a global account which was associated with multiple SIDs
2) Updated user account to one that was associated with a single SID
When I updated the account to another one that was again a global account that was associated with a single SID. With this change, the deployment was successful
3) Will use a technical user
Our team will be provisioning a technical user and updating our destinations to this new user will be our next step.
User | Count |
---|---|
34 | |
21 | |
9 | |
8 | |
5 | |
4 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.