-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use in reusable workflow: Error: The security token included in the request is invalid.
#383
Comments
@choffa Did you find a workaround? I am also facing this issue. |
@choffa Please let me know if you find a workaround. I am having the same issue |
@jim-hill-r @drey0143143 No, I was not able to find a good workaround for this issue. We decided to accept the duplication for now. |
I was having a problem with Azure credentials which seem similar to the one above. I was able to solve it following the steps at the link below: In short, it suggests to have the credentials in an environments and pass the environment as a parameter by the caller workflow. |
I'm facing the same issue |
I suspect this would be due to existing credentials within the runner, or lack thereof. I'm not super experienced with reusable workflows, but I'd like it if the people running into this could check if their environment variables are populated at the time the configure-aws-credentials step runs. If you upgrade to If there's no issue with inputs, and there's no unexpected environment variables in the runner, then I'm not sure why a composite action would be failing and would need to look more into it. |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
The project where I faced this issue has since been cancelled, so I now have no way to test @peterwoodworth 's suggestion. |
Yesterday, I started creating an AWS SAM CI/CD pipeline using GitHub Actions, which isn't yet deployed. Today, the mbland/elistman pipeline started failing while trying to configure AWS credentials after pushing commit 4841ade: - https://github.com/mbland/elistman/actions/runs/6149590436/job/16686549484 Error: The security token included in the request is invalid. I tried to update the trust policy for the relevant IAM user, which I'd seen had been updated to trust requests from mbland/ses-forwarder. I manually edited it back to mbland/elistman. Rerunning the job still failed. I then updated the pipeline to aws-actions/configure-aws-credentials@v3 in commit 60463bc, but it still failed: - https://github.com/mbland/elistman/actions/runs/6149930473/job/16686849270 Searching for related issues turned up the possibility of trying "unset-current-credentials: true": - https://github.com/aws-actions/configure-aws-credentials#unset-current-credentials - aws-actions/configure-aws-credentials#383 Trying it to see how it goes.
In that case, please feel free to open a new issue if anyone encounters any problems on |
Comments on closed issues are hard for our team to see. |
I have been trying to use this action in a reusable workflow. Whenever I try to I get an
Error: The security token included in the request is invalid.
My motivation for using the action in this way, is to be able to do the same workflow on different accounts, depending in the circumstances, such as deployingdev
on push, andprod
manually.Reproduction steps:
My called (reusable) workflow looks as follows:
And the caller workflow looks like:
Expected behaviour
I expect the action to work as normal, like it does when used directly, ie.
Using the action this way works just fine. That also confirms that it is not the secrets that are the issue...
Let me know if you need anything else! :)
The text was updated successfully, but these errors were encountered: