Azure / Azure/azure-workload-identity
Add CLI tool for setting up OIDC URL in unmanaged clusters
- Dominant language
- Go
- Stars
- 337
- Forks
- 122
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 3
Description
```
* Setup a storage account
* Create discovery json and upload to .well-known/openid-configuration
* Create keys json and upload to openid/v1/jwks
* E2E testing (pre-release for the tool)
* Unit test coverage
* Document command usage
* This is mostly for unmanaged clusters (AKS-engine)/CAPZ
* Handle rotation of signing key
* Appending the new key to jwks
* Removing the new key from jwks after 24h
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the proposed CLI entry point and the existing OIDC, storage-account, AKS-engine, or CAPZ integration areas. Define the command's setup and signing-key rotation behavior from the checklist, then add unit and E2E coverage and document command usage. Done means unmanaged clusters can publish the discovery and JWKS documents and rotate keys safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- authentication, cli, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100