feat: implementation of logout functionality#838
Open
Akhileswara-Microsoft wants to merge 9 commits intodevfrom
Open
feat: implementation of logout functionality#838Akhileswara-Microsoft wants to merge 9 commits intodevfrom
Akhileswara-Microsoft wants to merge 9 commits intodevfrom
Conversation
…Header to use LoginButton
…Context to fetch user email from claims
Akhileswara-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
malrose07,
nchandhi and
toherman-msft
as code owners
Akhileswara-Microsoft
had a problem deploying
to
production
GitHub Actions
Failure
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Azure Easy Auth–backed authentication state to the React frontend and updates the header UI to show a user avatar with a sign-out menu.
Changes:
- Introduces an
AuthContext(AuthProvider+useAuth) that reads user claims from/.auth/meand exposes login/logout redirects. - Adds a
LoginButtoncomponent that renders an avatar-based menu with a “Sign out” action. - Wraps the app in
AuthProviderand swaps the header avatar for the new component.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| src/App/src/main.tsx | Wraps the app with AuthProvider so auth state is available globally. |
| src/App/src/contexts/AuthContext.tsx | New context for Easy Auth user loading + login/logout redirects. |
| src/App/src/components/LoginButton.tsx | New header avatar/menu UI for user display and sign-out. |
| src/App/src/components/AppHeader.tsx | Replaces the previous Avatar with LoginButton. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Akhileswara-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
… remove AuthContext
Akhileswara-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
…-label on LoginButton buttons Agent-Logs-Url: https://github.com/microsoft/content-generation-solution-accelerator/sessions/22315c19-138c-49fc-9d54-060a30972272 Co-authored-by: Akhileswara-Microsoft <234037885+Akhileswara-Microsoft@users.noreply.github.com>
Akhileswara-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Akhileswara-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
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.
Purpose
This pull request refactors how user authentication and profile information are handled in the app header. The user avatar and login/logout functionality are now encapsulated in a new
LoginButtoncomponent, which provides a user menu and displays the user's name and email. Additionally, user email is now fetched and stored in the Redux state, and the header code has been simplified as a result.These changes make the app header more modular and user-friendly, and improve robustness and clarity in handling user authentication data.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation