-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid CSRF token provided : Import source modifiers form #2935
Comments
Same here - I just have put an "return true;" into CsrfCounterMeasure.php and restarted apache ... of course I cannot recommend this workaround |
ref/NC/838215 |
Yeah, unless you want to deliberately open GHSA-3mwp-5p5v-j6q3 again |
It's incompatible with gipfl`s… fixes #2935
Oh and, since this is a widely used library part, disable CSRF token verification for all recent Icinga Web products. This is really one of the worst workarounds I've encountered. Instead, please use my solution I just referenced. |
It's incompatible with gipfl`s… fixes #2935
ref/NC/838868 |
It's incompatible with gipfl`s… fixes #2935
Current Behavior
Within Director, I am editing an import source. I want to add a modifier. After adding some text to "Property" and "Target property" fields, I am receiving an error.
Invalid CSRF token provided (CsrfCounterMeasure.php:30)
Possible Solution
We are on the latest version, 1.11.2. Mabe #2893 has something to do with this.
Steps to Reproduce (for bugs)
Install Director 1.11.2. Add an import source. Click on "modifiers" tab. Click "+Add", enter a property, click on target property and see the error.
Your Environment
Stacktrace
The text was updated successfully, but these errors were encountered: