This repository has been archived by the owner on Aug 20, 2023. It is now read-only.
2-Factor Authentication doesn't work if account does not exist #82
Labels
Bug
Something isn't working how it should.
CloudLink
Inquiries related to CloudLink.
Server-Side
Improvements or fixes to server-side code.
URGENT
An urgent EMERGENCY.
Comments
MikeDev101
added
Bug
Something isn't working how it should.
CloudLink
Inquiries related to CloudLink.
URGENT
An urgent EMERGENCY.
Server-Side
Improvements or fixes to server-side code.
labels
Nov 28, 2021
cww2010 |
Rix56 |
Possible dirty server workaround for the time being: Try-catch the part that errors and then create an account with a nulled password automatically |
Also, |
meguy7878 |
all added |
bluepig600 |
already exists |
Voxalice |
samq64 |
Added |
I can log in now, but get an internal server error when reaching the home page. |
As of now, I would wait for the server to be upgraded to the latest build of CloudLink. |
closing as gone stale and will be fixed in next build |
Touchcreator |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Bug
Something isn't working how it should.
CloudLink
Inquiries related to CloudLink.
Server-Side
Improvements or fixes to server-side code.
URGENT
An urgent EMERGENCY.
After debugging the issue in #77, we determined the issue of accounts being unable to sign in related to some lack of checks. If an account doesn't exist in the server, and a user tries to authenticate with 2FA, it will throw up a "bool obj not subscriptable" error.
The workaround, for the time being, is creating a dummy account with a NULLED password. Simply state your scratch username (MUST BE VERBATIM, AS IT IS CASE-SENSITIVE) and I will manually add your account until this issue is fixed.
The text was updated successfully, but these errors were encountered: