Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate the discrepancy between authorized users in LDAP and EasyCLA #4394

Closed
mlehotskylf opened this issue Jul 26, 2024 · 4 comments
Closed
Assignees
Labels

Comments

@mlehotskylf
Copy link
Contributor

Investigate the discrepancy between authorized users in LDAP and in EasyCLA

More info: https://docs.google.com/document/d/1WFBjBC-_EYBNmaVTWIvAJ3ygMI0C-npV9GMXF2CgPYg/edit#heading=h.dopp1s54sg26

@nickmango
Copy link
Collaborator

Resolved the issue regarding ecla fetches for users that was a part cause for the discrepancy. This is to be verified by Eric in his script file that checks the authorized api.
cc @mlehotskylf

@mlehotskylf
Copy link
Contributor Author

@nickmango to review EasyCLA event log and find if any of these users (which are on LDAP only) have any records there being added as contributors or CLA managers.

nickmango added a commit to nickmango/easycla that referenced this issue Aug 28, 2024
- Script that checks activity logs for a project and lfusername

Signed-off-by: Harold Wanyama <[email protected]>
nickmango added a commit that referenced this issue Aug 28, 2024
@mlehotskylf
Copy link
Contributor Author

See 4451 for more details.

@mlehotskylf
Copy link
Contributor Author

We already know the discrepancy between LDAP and EasyCLA and its reason so closing this ticket. Next step will be review users which are not authorized by EasyCLA one by one and fix their record in DynamoDB and ask them to fix it. This will be tracked in separate ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants