Action parameters required for Organisation ID and Repository ID
- Dominant language
- TypeScript
- Stars
- 552
- Forks
- 440
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 18
Description
A change in the GitHub Enterprise Cloud OIDC was made, now requiring Organisation ID and Repository ID upon creation:
However azure/login has no support for these parameters, still sending the auth request using the old Subject Identifier:
`repo:TestOrg/test-repo:pull_request`
This mismatch in Subject Identifiers will result in the error:
`No matching federated identity record found for presented assertion subject`
Please add parameters for Organisation ID and Repository ID, so the Subject Identifier is up to date.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing azure/login's OIDC authentication request and how its Subject Identifier is assembled. Locate the parameter handling and verify that Organisation ID and Repository ID are accepted and included in the updated Subject Identifier; confirm the request no longer produces the reported federated identity mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, typescript
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100