-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for Google Authentication in the Web Version of Threat Dragon #1173
Comments
Thanks for this enhancement @priyankaChauhan2804 , hope that it can be implemented in either version 2.4 or 2.5 but when ever you are ready |
your welcome @jgadsden ! Could you assign me this issue so I could work on it? |
Hi @priyankaChauhan2804, I'd like to know if you're still actively working on it. If you’re no longer able to work on it or would like some help, I’d be interested in taking it on. I’ve been looking for a good opportunity to contribute to this project, and this issue aligns well with my interests/skills. |
hello @MaahiKhazi , yes actually i am currently invested in my exams so i wasn't able to work on this issue. You can take it up as i don't think i'll be able to give it time as of this month :) |
I am currently working on a fix for this. |
yes, apologies, I agree @ericfitz you did say in our video call last month that you are working on this issue - assigned to you |
Describe what problem your feature request solves:
Description:
I was using the web version of Threat Dragon and noticed that Google authentication is not available as a sign-in option.
Steps to Reproduce:
Visual Representation:
Expected Behaviour:
The application should support Google authentication to make signing in more accessible for users with Google accounts.
Describe the solution you'd like:
Introduce support for Google authentication in the web version of Threat Dragon by integrating Google OAuth2. This would allow users to log in with their Google accounts, enhancing accessibility and user convenience.
The text was updated successfully, but these errors were encountered: