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
Describe the bug
When attempting to log in to the OSS Insight website, the login process is not functioning correctly. Despite selecting a login option (GitHub, Google, etc.), the login popup remains on the screen and no further action is taken, preventing me from accessing my account.
Click on that upper_left button seems to be for logging in.
The browser pops up a login page with three option to choose(GitHub,Google and so on)
No matter click which button,nothing happened.The login popup remains on the screen without any further action, and the login process does not proceed.
Expected behavior
I can log in to my account through GitHub account or others.
Desktop (please complete the following information):
OS: Windows 11
Browser Chrome
Version 127.0.6533.120(64 bit)
(And newest Edge do so)
The text was updated successfully, but these errors were encountered:
Does this question still exist? The pop-up window is a login page hosted on Auth0, and I am not sure if it is due to a malfunction in Auth0 that caused a short-term inability to log in.
Does this question still exist? The pop-up window is a login page hosted on Auth0, and I am not sure if it is due to a malfunction in Auth0 that caused a short-term inability to log in.
The quesiton still exist now,I just tried it.From personal perspective,it is very likely because of Auth0.
Bug Report
Describe the bug
When attempting to log in to the OSS Insight website, the login process is not functioning correctly. Despite selecting a login option (GitHub, Google, etc.), the login popup remains on the screen and no further action is taken, preventing me from accessing my account.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I can log in to my account through GitHub account or others.
Desktop (please complete the following information):
(And newest Edge do so)
The text was updated successfully, but these errors were encountered: