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
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MySQL 8.0.30
Did you add customize OAuth?
YES, For Facebook Login, following documentation for Login with Yahoo
What happened?
Issue Description
I am encountering a problem when a user who has been soft-deleted attempts to log in using OAuth (Google). I receive the following error:
Steps to Reproduce
Soft delete a user.
The user attempts to log in again using OAuth (Google) with the same email.
Expected Output
I would expect the system to handle this situation gracefully, either by permanently deleting the entry for the soft-deleted user or by reactivating the user when they attempt to log in again, or by displaying a notification that the user has previously registered and been deleted by an admin, prompting them to contact the admin for further assistance.
PHP Version
8.2.22
CodeIgniter4 Version
4.5.4
Shield Version
1.1.0
Shield OAuth Version?
dev-develop
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MySQL 8.0.30
Did you add customize OAuth?
YES, For Facebook Login, following documentation for Login with Yahoo
What happened?
Issue Description
I am encountering a problem when a user who has been soft-deleted attempts to log in using OAuth (Google). I receive the following error:
Steps to Reproduce
Expected Output
I would expect the system to handle this situation gracefully, either by permanently deleting the entry for the soft-deleted user or by reactivating the user when they attempt to log in again, or by displaying a notification that the user has previously registered and been deleted by an admin, prompting them to contact the admin for further assistance.
Anything else?
log-2024-09-27 copy.log
The text was updated successfully, but these errors were encountered: