Tools
Error displays in the Web Help Desk Mobile application
This article addresses an error that displays in the Web Help Desk Mobile application when logging in to Web Help Desk 12.7.4.
First published date
Last published date
Overview
Product section
Cause
- The mobile application cannot initiate Cross-Site Request Forgery (CSRF) protection to the Web Help Desk server.
- PREFERENCES table was missing a lot of settings
Resolution
Add a new Java property in the targeted configuration file that disables CSRF protection between the mobile application and the Web Help Desk server. When finished, restart Web Help Desk and verify that the error message is no longer displayed in the mobile application.
Note: CSRF protection is enabled when techs and clients connect to the Web Help Desk server using a supported web browser.
Modify the targeted configuration file.
Add a new Java property to the targeted configuration file based on your operating system.Microsoft Windows Server
- Navigate to <WebHelpDesk>\bin\wrapper\conf and open the wrapper_template.conf file in a text editor (such as Notepad).
- In the file, scroll down to Java Additional Parameters.
- Locate the last Java property number in this section. For example, 18.
- Add the following Java property to this section:
- wrapper.java.additional.19=-DWHDDisableCsrfCheckMobile=true
- where 19 is the next incremented parameter and DWHDDisableCsrfCheckMobile=true disables the CSRF function for the mobile application.
- Save and close the file.
macOS or Linux
- Navigate to <WebHelpDesk>\conf and open the whd.conf file in a text editor.
- In the file, scroll down to JAVA_OPTS.
- Add the following Java property to this section:
- "-DWHDDisableCsrfCheckMobile=true"
- Save and close the file.
Restart Web Help Desk
- Stop the Web Help Desk service.
- Restart Web Help Desk.
- Start the Web Help Desk service.
Verify the update
- Open Web Help Desk Mobile.
- Log in to Web Help Desk.
- Verify that the error message no longer displays in the application.
Resolution for Cause 2:
1. Restore our database to a new database and then copy over the records from the PREFERENCES table back into the live database.
2. Restart the WHD service
3. Verify if the issue is resolved.