Authentication through Google account #111
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@muskan6769 , Are you still working on this? |
|
Nice work 👍 The issue might be that a user has to sign up for our custom authentication but sign-up again for our Discourse instance which is an integral part. It will be nice to have a single authentication system. For this, Discourse comes with its own SSO system which we can use from this purpose. This will have the advantage that we will have single authentication system and we can focus more on features built over user activity. Kindly take a look at it and let us know your thoughts. 👍 |
|
@AdiChat I understood the issue....I'll work on it. |
|
@AdiChat.. Should I work upon ldap authentication.? |
|
@muskan6769 Yes, you may proceed with it. 👍 |
winlover32
approved these changes
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
developbranch.Which issue does this PR fix?:
fixes: #59
"First step for issue #59(Authentication through google account)
Why do we need this PR?:
To see the search history of any user ,we need his authentication first.
If relevant, please include a screenshot.
Demo (optional):
Some tips for you to write the instructions:
Testing instructions:
If there is any work still left to do, please add it here.
TODOs (if any):