redhat-cop / redhat-cop/group-sync-operator
Managed Identity in place of Client secret
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Can Groupsync operator authticate with Azure AD using managed identity instead of secret with client ID and client secret to achieve password less authentication ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the operator's current Azure AD authentication configuration and how client ID and client secret values are consumed. Then determine the managed-identity entry point and required configuration changes; done means Groupsync authenticates without a client secret and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100