I am not getting the access token for my MERN app deployed in Azure webapp. I can see ARRAffinity, ARRAffinitySameSite, refreshToken but access token is missing why?

Question

I am not getting the access token for my MERN app deployed in Azure webapp. I can see ARRAffinity, ARRAffinitySameSite, refreshToken but access token is missing why?

Vishal 0

for my MERN application, in browser nerwork tab, I can see : ARRAffinity, ARRAffinitySameSite, refreshToken but I cant see access token, because of this I cant logi to my application, although my application is not down, but I cant enter into application by putting user and password.

these are my settings:-

Stack: Node

Startup Command: npm start

SCM Basic Auth Publishing: ON

FTP Basic Auth Publishing: ON

FTP state: FTPS only

Inbound IP mode: IPV4

HTTP version: 2.0

HTTP 2.0 Proxy: OFF (When this setting is enabled, front end will forward HTTP 2.0 traffic to the worker enabling scenarios like GRPC.)

SSH: ON

Always on: ON (Prevents your app from being idled out due to inactivity)

Session affinity: OFF, (I have tried with Turn Session Affinity ON also) (Improve performance of your stateless app by turning Affinity Cookie off, stateful apps should keep this setting on for compatibility.)

Session affinity proxy: OFF (Adjust the Affinity Cookie domain to the reverse proxy domain.)

HTTPS Only: ON/OFF (Enable this feature to redirect all HTTP traffic to HTTPS.)

Anonymous

2026-01-01T23:25:27.5166667+00:00

Hi @Vishal

Thank you for your question.

Based on the details you shared, this behavior is generally expected and does not indicate that your application is down.

Seeing ARRAffinity and ARRAffinitySameSite cookies is normal when your MERN application is hosted on Azure App Service. These cookies are used by Azure for session affinity and are not related to authentication. In many secure authentication implementations, the access token is not exposed to the browser. Access tokens are short-lived and are often kept server-side or handled internally, while the browser may only receive a refresh token or a secure session cookie.

The login issue usually happens due to a configuration problem rather than a missing access token in the Network tab. Common causes include incorrect cookie settings (such as SameSite or Secure flags), frontend and backend running on different domains without withCredentials enabled, or a mismatch in how the backend issues tokens after validating the username and password. If App Service Authentication (Easy Auth) is enabled, Azure manages the tokens internally and your Node.js API must rely on the identity headers provided by the platform instead of expecting an access token from the browser.

I recommend checking that your login API either returns a valid session or access token correctly, verifying cookie and CORS settings, and confirming whether App Service Authentication is enabled and aligned with your MERN authentication logic. Not seeing the access token in the browser is normal; fixing the auth configuration should allow users to log in successfully.

Hope this helps, and please feel free to post back if you need further assistance.
Vishal 0 Reputation points

2026-01-02T04:48:50.05+00:00

@Anonymous , Thanks for your quick reponse, but honestly, for subscription my autopay got failed for 1 day so I manually paid it, after that problem started, before it was working fine, same code. I tried to redeploy the application, also. There is nothing change from the code side. I am using B2 plan.
As frontend and backend is deployed in same webapp actually this is my admin panel for other applications running.
True my application is running only I am not able to login to my admin panel, and if I restart my application it works fine for sometime like 30mins or 1 hour (when it has access token) but after the access token expire lets say in 30mins I am not able to login to my admin panel again.
I means my browser it not getting the access token from Azure right? but on the other hand it is getting the: ARRAffinity, ARRAffinitySameSite.

Your answer

Anonymous

2026-01-01T23:25:27.5166667+00:00

Hi @Vishal

Thank you for your question.

Based on the details you shared, this behavior is generally expected and does not indicate that your application is down.

Seeing ARRAffinity and ARRAffinitySameSite cookies is normal when your MERN application is hosted on Azure App Service. These cookies are used by Azure for session affinity and are not related to authentication. In many secure authentication implementations, the access token is not exposed to the browser. Access tokens are short-lived and are often kept server-side or handled internally, while the browser may only receive a refresh token or a secure session cookie.

The login issue usually happens due to a configuration problem rather than a missing access token in the Network tab. Common causes include incorrect cookie settings (such as SameSite or Secure flags), frontend and backend running on different domains without withCredentials enabled, or a mismatch in how the backend issues tokens after validating the username and password. If App Service Authentication (Easy Auth) is enabled, Azure manages the tokens internally and your Node.js API must rely on the identity headers provided by the platform instead of expecting an access token from the browser.

I recommend checking that your login API either returns a valid session or access token correctly, verifying cookie and CORS settings, and confirming whether App Service Authentication is enabled and aligned with your MERN authentication logic. Not seeing the access token in the browser is normal; fixing the auth configuration should allow users to log in successfully.

Hope this helps, and please feel free to post back if you need further assistance.
Vishal 0 Reputation points

2026-01-02T04:48:50.05+00:00

@Anonymous , Thanks for your quick reponse, but honestly, for subscription my autopay got failed for 1 day so I manually paid it, after that problem started, before it was working fine, same code. I tried to redeploy the application, also. There is nothing change from the code side. I am using B2 plan.
As frontend and backend is deployed in same webapp actually this is my admin panel for other applications running.
True my application is running only I am not able to login to my admin panel, and if I restart my application it works fine for sometime like 30mins or 1 hour (when it has access token) but after the access token expire lets say in 30mins I am not able to login to my admin panel again.
I means my browser it not getting the access token from Azure right? but on the other hand it is getting the: ARRAffinity, ARRAffinitySameSite.