Infos:
- Used Zammad version: 6.0
- Used Zammad installation type: (source, package, docker-compose, …) package
- Operating system: Debian 10.10
- Browser + version:
Chrome, Edge, Firefox, private windows, to no avail
Expected behavior:
- Users failed to log in to Zammad and showing them 422 errors, there should be a link or simple steps telling them how to fix the issue instead of asking for help from IT Department all the time.
Actual behavior:
- Users failed to log in to Zammad and showing them 422 errors, confusing the end users very often
Steps to reproduce the behavior:
This kind of issues occurred from time to time and most users are totally lost, don’t really know what is wrong as they will just keep trying to log in with the same browser and the issue persists.
The 422 message is normally “422: The change you wanted was rejected.
Message from microsoft offce365: csrf detected”
