You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Many of our customer still use Classic Azure DevOps pipelines (as opposed to YAML pipelines) and therefore the classic tasks that come with the AWS Toolkit for Azure DevOps are also used. While trying a conversion of one of these pipelines to use a Service Connection with OIDC authentication enabled I can't seem to get past the following error: "Failed to assume role with OIDC: Error: System.AccessToken is undefined."
Here's a log excerpt with error in context:
Content uploads are performed using S3's PutObject API and/or the multi-part upload APIs. The specific APIs used depend on the size of the individual files being uploaded.
2024-08-30T20:12:30.8854418Z ==============================================================================
2024-08-30T20:12:31.5474060Z Configuring credentials for task
2024-08-30T20:12:31.5480739Z ...configuring AWS credentials from service endpoint '7e45a58e-redacted'
2024-08-30T20:12:31.5480974Z Skipping Instance profile, we have OIDC enabled
2024-08-30T20:12:31.5491876Z ...configuring AWS credentials from service endpoint '7e45a58e-redacted'
2024-08-30T20:12:31.5493003Z Getting OIDC Token...
2024-08-30T20:12:31.5499826Z Failed to assume role with OIDC: Error: System.AccessToken is undefined
.
.
.
To reproduce
Create an AWS Service Connection with "Use OIDC" enabled
Create a classic Azure DevOps pipeline with an S3 Upload task in it and configure that task to use the service connection from step 1
Run the pipeline it will fail
Expected behavior
The S3 Upload task should work
Screenshots
Your Environment
On-prem or cloud based?: Cloud
Azure DevOps version: Whatever version is used in the cloud
AWS Toolkit for Azure DevOps version: 1.15.0 (Latest)
Additional context
I tried the S3 Upload tasks using a YAML pipeline (same service connection and target S3 bucket) and it worked!
The text was updated successfully, but these errors were encountered:
Describe the bug
Many of our customer still use Classic Azure DevOps pipelines (as opposed to YAML pipelines) and therefore the classic tasks that come with the AWS Toolkit for Azure DevOps are also used. While trying a conversion of one of these pipelines to use a Service Connection with OIDC authentication enabled I can't seem to get past the following error: "Failed to assume role with OIDC: Error: System.AccessToken is undefined."
Here's a log excerpt with error in context:
To reproduce
Expected behavior
The S3 Upload task should work
Screenshots
Your Environment
Additional context
I tried the S3 Upload tasks using a YAML pipeline (same service connection and target S3 bucket) and it worked!
The text was updated successfully, but these errors were encountered: