Description:
I've been using the actions-oidc-debugger successfully in the past, but recently, without any changes to my configuration, it has stopped working and now returns a Forbidden error when attempting to authenticate using OIDC.
Error Message:
received non-200 from jwt api: Forbidden
Configuration:
Here's the relevant part of the GitHub Actions workflow configuration, which is closely based on the official documentation:
jobs:
debug-oidc:
permissions:
contents: read
id-token: write
runs-on: [self-hosted, micro]
steps:
- name: Checkout actions-oidc-debugger
uses: actions/checkout@v3
with:
repository: github/actions-oidc-debugger
ref: main
path: ./.github/actions/actions-oidc-debugger
- name: Debug OIDC Claims
uses: ./.github/actions/actions-oidc-debugger
with:
audience: 'https://github.com/github'Expected Behavior:
The OIDC authentication should complete successfully as it had in the past, allowing the workflow to proceed without authentication errors.
Actual Behavior:
The workflow fails during the OIDC authentication step with a Forbidden error, indicating a lack of permission or other authorization issues.
Additional Context:
No changes were made to the GitHub Actions permissions or runner configuration prior to the onset of this issue.
This issue started occurring recently, suggesting a possible external change in the handling of OIDC requests or a change in API behavior.
Can you validate it still works the same on your side ?
Description:
I've been using the actions-oidc-debugger successfully in the past, but recently, without any changes to my configuration, it has stopped working and now returns a
Forbiddenerror when attempting to authenticate using OIDC.Error Message:
Configuration:
Here's the relevant part of the GitHub Actions workflow configuration, which is closely based on the official documentation:
Expected Behavior:
The OIDC authentication should complete successfully as it had in the past, allowing the workflow to proceed without authentication errors.
Actual Behavior:
The workflow fails during the OIDC authentication step with a Forbidden error, indicating a lack of permission or other authorization issues.
Additional Context:
No changes were made to the GitHub Actions permissions or runner configuration prior to the onset of this issue.
This issue started occurring recently, suggesting a possible external change in the handling of OIDC requests or a change in API behavior.
Can you validate it still works the same on your side ?