build(deps): Bump @babel/traverse from 7.16.7 to 7.23.3 #84
Annotations
1 error, 1 warning, and 2 notices
Error: Forbidden: Unable to find a role named `arn:aws:iam::000000000000:role/doesnotexist`, it has likely not been defined in the `saml-to.yml` within https://github.com/saml-to/assume-aws-role-action
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Unable to assume the role with an ARN of `arn:aws:iam::000000000000:role/doesnotexist`.
Please ensure all of the following:
1) the SAML Provider Metadata in AWS IAM is correct. It can be obtained by downloading it from: https://saml.to/metadata/github/saml-to
2) the SAML Provider ARN is correct in the `saml-to.yml` configuration file, and in the format of `arn:aws:iam::ACCOUNT_ID:saml-provider/PROVIDER_NAME`,
3) the Role ARN (arn:aws:iam::000000000000:role/doesnotexist) is correct in the `saml-to.yml` configuration file, and in the format of `arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME`
4) the Role (arn:aws:iam::000000000000:role/doesnotexist) has the correct Trust Relationship , which can be found by opening the Role in AWS IAM, choosing the Trust Relationship tab, editing it to ensure it's in the following format:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Federated": "YOUR_PROVIDER_ARN"
},
"Action": "sts:AssumeRoleWithSAML",
"Condition": {
"StringEquals": {
"SAML:aud": "https://signin.aws.amazon.com/saml"
}
}
}
]
}
If a provider or role hasn't been created or configured yet, please follow the configuration instructions: https://github.com/saml-to/assume-aws-role-action/blob/main/README.md#configuration
|
|
The logs for this run have expired and are no longer available.
Loading