Remote Exception Not a valid CSRF token

[CRIS162]

After performing an update for the expedition beta, and updating the ubuntu OS using apt-get update I was unable to use the expedition tool due to this certificate issue. In expedition internal check I have no status errors that could relate me to the cause of the issue. What are the possible cause and resolutions to this error? 

[azuniga]

This is a security measure built into expedition, do you have this same problem in another browser or in incognito mode?

[Rashawne]

Make sure you are using an up-to-date browser.

Make sure your browser accepts cookies.

Depending on your browser settings, you may have to enable them explicitly.

Clear your cache and remove all cookies from your browser. Refresh the page.

Provitalize

[CRIS162]

Hello,

I have attempted this on many browsers including edge, mozilla, internet explorer, and chrome. Other users have attempted expedition but failed to log in due to the same error received. Are there potential certificate changes we can make to resolve this issue?

[lychiang]

@CRIS162 Trying remove the cookies setting of Expedition in the browser and restart the browser again , you will double click on the "NotSecure"on the URL bar , it will take you to the cookies setting. try to remove all the cookies there. 

 

[CRIS162]

Clearing the cache as well as any cookies related to this site did not resolve the issue. I attempted resetting my settings on Mozilla with no luck. 

[slp-security]

Hi all,

I installed Expedition in docker mode (deployed ON AWS). From LAN side (via IPSec VPN), no issue... If I use AWS ELB+WAF, so CLIENT->AWS ELB+WAF-> DOCKER+EXPEDITION, I received CSRF Token error... Clearer the cache of the browser doesn't help... Any idea ??

Regards,

HA

[azuniga]

Hello @slp-security 

What about if you change your ELB settings to be a persistent connection?

[Tom.Fenner]

Did you ever figure this out? I've got this issue on a new install using a on prem vm with a direct connection to it in the browser. Clearing cache/cookies has no effect. 

[Christopher.Felix]

Unfortunately no, I pivoted away from using expedition. However, rebuilding the VM or fixing the cert error may be the solution