Fix frontend WebAPI auth always failing in ApiAuthenticationService#679
Draft
Fix frontend WebAPI auth always failing in ApiAuthenticationService#679
Conversation
…int metadata Agent-Logs-Url: https://github.com/grandnode/grandnode2/sessions/8cd5622c-507d-4e12-9bec-6ba9d652cf52 Co-authored-by: KrzysztofPajak <16772986+KrzysztofPajak@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix frontend webapi auth always failing
Fix frontend WebAPI auth always failing in ApiAuthenticationService
Apr 26, 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.
IsApiFrontAuthenticated()always returnedfalsebecause it checked for[Authorize(AuthenticationSchemes = "FrontAuthentication")]on the endpoint metadata — but no web store endpoints carry that attribute.Changes
ApiAuthenticationService.IsApiFrontAuthenticated(): Replace the endpoint metadata inspection with an actualAuthenticateAsync(FrontendAPIConfig.AuthenticationScheme)call. If the JWT was signed with the frontend secret key, the scheme handler validates it and returns success.booltoasync Task<bool>; call site updated toawait.Microsoft.AspNetCore.Authorizationimport.ASP.NET Core caches auth results per request, so the subsequent
AuthenticateAsynccall insideApiCustomer()incurs no extra overhead.