External login screen problem
(Created page with "If you find that a user is unable to login with an external login provider getting stuck in the Register page, it's probably due to that there's an old or incorrect SysUser or...") |
(Automatically adding template at the end of the page.) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
If | If a user is unable to log in with an external login provider and is getting stuck on the Register page, it is probably due to old or incorrect SysUser or SysExternalLogin objects in the database. | ||
Do this | Do this: | ||
# Please note that if | # Please note that if your application is running, the user should log out and close their browsers. | ||
# Remove all previous SysUser and SysExternalLogin objects | # Remove all previous SysUser and SysExternalLogin objects - preferably from inside your application to make the syncing of objects remove them from the server memory. If you need to do it from the database directly, restart the Turnkey server or wait at least 15 minutes for the objects to be removed from running EcoSpaces. | ||
# If the external login is with Google (for example), | # If the external login is with Google (for example), ask the user to also go to their Google account view and remove the application approval for your application. | ||
After these steps, the correct SysUser and SysExternalLogin objects should be recreated the next time the user authenticates with the social login service. | After these steps, the correct SysUser and SysExternalLogin objects should be recreated the next time the user authenticates with the social login service. | ||
[[Category:Security]] | |||
{{Edited|July|12|2024}} | |||
Latest revision as of 15:34, 10 February 2024
If a user is unable to log in with an external login provider and is getting stuck on the Register page, it is probably due to old or incorrect SysUser or SysExternalLogin objects in the database.
Do this:
- Please note that if your application is running, the user should log out and close their browsers.
- Remove all previous SysUser and SysExternalLogin objects - preferably from inside your application to make the syncing of objects remove them from the server memory. If you need to do it from the database directly, restart the Turnkey server or wait at least 15 minutes for the objects to be removed from running EcoSpaces.
- If the external login is with Google (for example), ask the user to also go to their Google account view and remove the application approval for your application.
After these steps, the correct SysUser and SysExternalLogin objects should be recreated the next time the user authenticates with the social login service.
This page was edited more than 11 months ago on 02/10/2024. What links here