aws_cognito: UserPoolIdentityProviderOidc doesn't support SecretValue for client secret
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 71
Description
### Describe the feature
Hello,
Small FR that would make the use of SecretValue more straightforward.
`UserPoolIdentityProviderOidc` needs a client secret value for deployment. As of now it only supports `string` value.
Compared to the generic one like `UserPoolIdentityProviderGoogle` who support `clientSecretValue`.
### Use Case
It would make the DX a bit better, simplifying the resolution. And also align with the other providers from the cognito package.
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.131.0
### Environment details (OS name and version, etc.)
MacOS
Contributor guide
Research direction
Start with UserPoolIdentityProviderOidc in the Cognito package and compare its client secret handling with UserPoolIdentityProviderGoogle, which already supports clientSecretValue. The work is complete when the OIDC provider accepts SecretValue consistently with the comparable provider and the relevant Cognito behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100