Blazor loses token when published but not locally. #1357
Unanswered
MikeBrownCygnia
asked this question in
Q&A
Replies: 1 comment
-
I can confirm that my var token = ........ line returns blank in Azure, when it returns with a value on localhost. This is the response to the following call to Graph Api {"error":{"code":"InvalidAuthenticationToken","message":"CompactToken parsing failed with error code: 80049217","innerError":{"date":"2021-07-29T14:02:06","request-id":"a04de0df-487c-4340-912d-a8acd838ea86","client-request-id":"a04de0df-487c-4340-912d-a8acd838ea86"}}} So the error is certainly with the token generation part when in Azure. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am currently using the tutorial here https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-blazor-server
The fetch data script for GraphApi / Mail.Read works perfectly on my local machine, howwever when I publish, it shows the data very quickly then seems to refresh, and the token becomes unauthorized, losing the data on page almost instantly.
I assume this may be due to the lifecycle of the Blazor page, and how this interacts with AzureAd differently with a local build. Any idea on how to persist this?
Beta Was this translation helpful? Give feedback.
All reactions