You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLOUDP-314903 [OIDC] CRD Config Propagation to Automation Config (#60)
# Summary
### Core Functionality Enhancements:
* Added a new authentication mechanism, `MongoDB-OIDC`, to the list of
supported mechanisms in the `authentication_mechanism.go` file.
* Introduced the `OIDCProviderConfigs` field in the `AutomationConfig`
struct and implemented logic to merge and apply OIDC configurations into
the deployment in the `automation_config.go` file.
* Removed default value for `groupClaim` because the value `groups` can
result in hard to debug misconfiguration.
### API and Configuration Updates:
* Added the `IsOIDCEnabled()` method in the `Security` struct and
`AuthResource` interface to check if OIDC is enabled.
* Updated the `Options` struct in the `authentication.go` file to
include `OIDCProviderConfigs`.
### Test Coverage:
* Added comprehensive test cases for OIDC provider configurations in
`automation_config_test.go`, including scenarios for merging, clearing,
and modifying configurations.
* Updated the `TestAutomationConfigEquality` test to include OIDC
provider configurations.
### JSON Configuration Example:
* Updated the `automation_config.json` test data file to include sample
OIDC provider configurations for testing purposes.
## Proof of Work
<!-- Enter your proof that it works here.-->
## Checklist
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [ ] Have you checked whether your jira ticket required DOCSP changes?
- [ ] Have you checked for release_note changes?
## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
* **blocking**: Must be addressed before approval.
* **follow-up**: Can be addressed in a later PR or ticket.
* **q**: Clarifying question.
* **nit**: Non-blocking suggestions.
* **note**: Side-note, non-actionable. Example: Praise
* --> no prefix is considered a question
---------
Co-authored-by: Lucian Tosa <[email protected]>
Co-authored-by: Lucian Tosa <[email protected]>
Co-authored-by: Anand <[email protected]>
Co-authored-by: Anand Singh <[email protected]>
returnv1.ValidationError("GroupsClaim has to be specified in OIDC provider config %q when using Group Membership authorization", config.ConfigurationName)
0 commit comments