Replies: 2 comments
-
|
@ptejado this is a perfect place to start a discussion about your issue. The error you are facing is that the login on SAP BTP does not work with the configuration you have made. This could have several reasons that ned to be sorted out:
Can you check these points to narrow down where the issues comes from? I think the GH action itself is correct, at least the output shows the expected content. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Christian, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
@lechnerc77, @vipinvkmenon,
We are not sure if this is the forum for sharing this issue, but we are configuring a Proof of Concept for using JWT logon and it is failing.
For our business as usual CI/CD we are using USER and PASSWORD logon, but we are interested in using JWT logon in order to avoid using passwords in githubs repos.
We've followed these links:
https://dev.to/vipinvkmenon/bye-bye-credentials-automate-btp-cloud-foundry-setup-with-terraform-using-github-actions-and-3m07
https://community.sap.com/t5/technology-blog-posts-by-sap/authenticating-github-actions-workflows-deploying-to-the-sap-btp-cloud/ba-p/14075047
It seems we are able to generate the JWT token in the corresponding workflow step:
But when we use it for logging on and executing a terraform plan through BTP_ASSERTION environment variable, we received the following generic error:
No information has been found in our IAS for that correlation ID.
How can we find out more using that correlation ID?
Does exist any additional variables for adding more debug addionally to ACTIONS_STEP_DEBUG and ACTIONS_RUNNER_DEBUG?
Many thanks for you collaboration.
Beta Was this translation helpful? Give feedback.
All reactions