-
Notifications
You must be signed in to change notification settings - Fork 1
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
Clean up user accounts in OCL staging/production #712
Comments
@snyaggarwal to get the list of unused migrated accounts for OCL v2 staging and production. We'll review and decide which should be inactivated |
@paynejd PFA the list of users last login before 2021-05-01 in production. It has their created date as well. So we can compare last_login and created date to get a better idea. |
One more report needed, which is content authored by users. It will further filter the above report. |
@paynejd to review the user list that Sunny sent over, then determine next steps |
@paynejd An OCL admin user can now do following for other users:
|
@snyaggarwal Should this be working on QA? I did a test in Postman and could not do either a hard or soft delete of a fake user that I made. I did |
@jamlung-ri I just did the hard delete on this api.qa.openconceptlab.org/users/fake/ through postman: |
Looks good! Not sure why I couldn't make it work before but I was able to do both soft and hard deletes. |
@paynejd On Prod users are deleted/deactivated based on the analysis you sent. The sheet is updated. |
A quick closeout on this between @paynejd and @snyaggarwal is needed, which we can do on tomorrow's Dev call. |
@paynejd this is also done for Staging |
We have several types of user accounts in OCL production/staging:
a. Signed into OCL (since May 1, 2021) and have authored some content ==> NO ACTION
b. Signed into OCL v2 (since May 1, 2021) but have not authored anything ==> NO ACTION
a. Legitimate accounts that have not signed into OCL v2, but have authored some content ==> DEACTIVATE
b. Legitimate accounts that have not signed into OCL v2 that have not authored any content ==> DEACTIVATE
c. Junk accounts that were migrated from OCL v1 ==> DELETE
@snyaggarwal pulled the list of accounts from staging/production, and we have tagged accounts as
NO ACTION
,DEACTIVATE
andDELETE
.The next steps are:
DELETE
DEACTIVATE
accounts, since OCL does not currently have a method to support thisDEACTIVATE
strategyThe text was updated successfully, but these errors were encountered: