Skip to main content

Why Am I Seeing "You Are Still Signed In" When Logging In AXP?

If you see a "You are still signed in, Sign in again?" or "Invalid CSRF token" message when SSO in AXP, this guide explains what it means and how to fix it. Relevant search terms: login error, CSRF token, sign in failed, session expired, AXP login issue.

Summary: This message appears when a security check fails during login — usually after clearing your browser cache, having multiple AXP tabs open, or a session timing out. You can resolve it in a few simple steps without needing to contact support.

Permissions Required: No special role required — this applies to all AXP users.


Troubleshooting Steps to follow

  1. On the login screen, click Sign in with Google — this usually works even when the error appears:

  2. If the error persists, close all open AXP browser tabs and open a fresh one before trying again.

  3. Clear your cookies and cache specifically for alliants.app:

    • In Chrome: press Esc → go to Third-party cookiesSee all sites and permissions → find alliants.app → delete its data.

    • This avoids clearing cookies for every other site you use.

  4. Return to alliants.app and try logging in again.

  5. If the issue continues, try opening AXP in an incognito/private window or a different browser.


Common Questions

Q: What does "Invalid CSRF token" mean?

A: CSRF stands for Cross-Site Request Forgery. AXP uses a hidden security token to verify that login requests genuinely come from you. If that token is missing, expired, or doesn't match — for example, after you've cleared your cache or had the login page open for a long time — you'll see this error. It's a security feature, not a bug, and doesn't mean your account has been compromised.

Q: Why does signing in with Google still work when I get this error?

A: Google's sign-in flow uses a separate authentication process that doesn't depend on the same browser token. So even if the standard SSO login triggers this error, clicking Sign in with Google on the same screen will typically succeed.

Q: Do I need to clear all my browser cookies to fix this?

A: No — you can clear cookies just for alliants.app. In Chrome, press EscThird-party cookiesSee all sites and permissions, then find and remove alliants.app. This targets only the AXP session without affecting your other sites.

Q: What causes this error in the first place?

A: The most common triggers are:

  • Clearing your browser cache or cookies

  • Having the login page open for a long time before submitting

  • Being logged into AXP across multiple tabs at the same time

  • A browser extension (such as an ad blocker or privacy tool) interfering with cookies

Q: What if none of these steps work?

A: Try logging in via an incognito/private window or a different browser entirely. If you're still unable to access AXP, contact your property's system administrator or reach out to AXP support.

Did this answer your question?