-
Notifications
You must be signed in to change notification settings - Fork 18
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
An error occurred (AccessDenied) when calling the AssumeRole operation: MultiFactorAuthentication failed with invalid MFA one time pass code. #216
Comments
@HADEED-143 can you please share more details, e.g. can you share the workflow? This seems to me like a config issue with AWS, because the wait-for-secrets action just makes a secret available in the workflow. Feel free to email [email protected] if you prefer that. |
Hey Varun, We are Running this workflow from last year there was no issue
and no change. From the Last Week on All Repository This Issue Raise. We
cant do any deployment because of it take credential and echo same
credentials stuck for a some minute and then fail 252 exit code. My
Question is this ! is this generic issue ? other users also have raise this
issue or just it is from us ? .
Thanks & Regards
Hadeed.
…On Thu, Jul 18, 2024 at 11:12 AM Varun Sharma ***@***.***> wrote:
@HADEED-143 <https://github.com/HADEED-143> can you please share more
details, e.g. can you share the workflow? This seems to me like a config
issue with AWS, because the wait-for-secrets action just makes a secret
available in the workflow.
Feel free to email ***@***.*** if you prefer that.
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOLY6QBGPZXW7H773VZWF2DZM5MDJAVCNFSM6AAAAABK36ZVE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZVG4YDENRUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No one else has raised it. I can see a recent successful run on a public repo as well: I recommend running a simple workflow to make sure you are getting the secret. If so, then looking at the error you are getting in the release workflow and investigating the root cause - this looks like a config issue with AWS. |
Now I am using the simple input mfa parameter for the workflow. For the
time being, i have removed all the securitystop check and commands in the
workflow.
The Sample File is attached below you can check for reference.
…On Thu, Jul 18, 2024 at 8:02 PM Varun Sharma ***@***.***> wrote:
No one else has raised it.
I can see a recent successful run on a public repo as well:
https://github.com/ghiscoding/slickgrid-react/actions/runs/9922211414/job/27411023267#step:11:13
I recommend running a simple workflow to make sure you are getting the
secret. If so, then looking at the error you are getting in the release
workflow and investigating the root cause - this looks like a config issue
with AWS.
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOLY6QBODTVY3RX6EMJ62OTZM7KJDAVCNFSM6AAAAABK36ZVE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZWHAYDKNBQG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I dont see the attachment, can you please attach it? |
Please check now. securitycheck.yaml name file is attached also with the
last email.
…On Fri, Jul 19, 2024 at 10:15 AM Varun Sharma ***@***.***> wrote:
I dont see the attachment, can you please attach it?
—
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOLY6QHQEYBCYZJWIYKTPCDZNCOG7AVCNFSM6AAAAABK36ZVE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZYGE3TIMRQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
We have Setup Our Personal Repository CD Pipeline with Github Actions. From last year it were Running Well. In the Last Week, For Build the Pipeline Prompt mfa step security echo mfa same . When Enter mfa shows Successfully set secrets!
Successfully cleared secrets. Then After 5 minute it shows the title error.
The text was updated successfully, but these errors were encountered: