aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::IAM::OIDCProvider should have client id resources to handle multiple apps on the same provider.
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::IAM::OIDCProvider
### Resource name
_No response_
### Description
OIDCProvider must be unique for a given URL, but if you are using any sort of hosted provider, you are likely to only be able to create one provider URL. For example, using Azure AD via Office 365, your provider URL is `https://login.microsoftonline.com/${TenantId}/v2.0` where the tenant id is unique to the account.
This is normally fine as you can simply attach each application's client id to the provider, but with cloudformation there's no way to do this right now without just lumping all the application client ids into the same stack, which makes deploying applications separately a pain. (Presumably the idea is there's a central "authorization stack" that is reviewed separately?)
The specific request would be to add an `AWS::IAM::OIDCClient` with properties like `{ ProviderId: String, ClientId: String }`.
### Other Details
_No response_
Contributor guide
Research direction
No repository files, tests, or implementation entry points are identified. Start by reviewing the AWS::IAM::OIDCProvider resource and the proposed ProviderId and ClientId properties, then determine the CloudFormation resource behavior and ownership needed for multiple applications. Done means the requested AWS::IAM::OIDCClient resource is specified and supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100