Task/269/log in using google auth/implement backend#281
Merged
Vasia1101 merged 20 commits intoJun 18, 2026
Conversation
…ttps://github.com/project-studying-dotnet/Streetcode-Server-May2026 into task/269/LogIn-using-Google-Auth/Implement-backend
…ttps://github.com/project-studying-dotnet/Streetcode-Server-May2026 into task/269/LogIn-using-Google-Auth/Implement-backend
Vasia1101
approved these changes
Jun 18, 2026
|
This file contains hidden or 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
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.



dev
JIRA
Code reviewers
Second Level Review
Summary of issue
Currently, there is no mechanism for users to authenticate via Google, which limits onboarding speed and user convenience.
Summary of change
Implemented Google OAuth authentication logic to streamline user sign-in. The following components were added/updated:
Controller: Added endpoint to handle Google authentication requests.
Mediator: Implemented handler logic to process the authentication flow.
DTOs: Defined Data Transfer Objects to handle incoming request payloads and outgoing responses.
Validators: Implemented FluentValidation/schema validation for incoming data to ensure integrity.
Unit Tests: Added comprehensive unit test coverage for the controller, mediator handlers, and validation logic.
Testing approach
Verified the authentication flow manually as both a guest and a returning user.
Ran all unit tests to ensure business logic integrity and edge-case handling.
Verified that the Google Client ID and API credentials are correctly injected via environment variables.
CHECK LIST