Certain requirements have user accounts being blocked automatically after a period of no site visits. As we manage our accounts in the client connected through OpenID Connect, a valid response from the client means the account is still in good standing. Therefore, to reduce the workload of our admins, we wanted the site to automatically unblock accounts that perform a successful authentication with the client.
1. Block an account that is still valid in the OIDC client.
2. Attempt to log in with that account using OIDC method.
3. See the "The username %name has not been activated or is blocked." message.
Add a new config option in the Advanced -> Security Implications section of the module config.
If the new config is enabled, have the portion of code that checks ->isBlocked() then perform an ->activate() instead of terminating with `return FALSE;`
Test the patch. Revise as needed.
New checkbox added to module config form.
This patch brought to you by the efforts of FDIC https://www.drupal.org/federal-deposit-insurance-corporation-fdic →
Needs review
3.0
Code
Thank you for contributing. It would help the maintainer and increase your changes for getting the change in, if you create a MR instead of a patch https://www.drupal.org/community/contributor-guide/task/create-a-merge-r... → The MR should apply against dev. not a specific version.