Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
The following instructions will walk you through setting up a Web Check for sites that use form-based authentication.
The exact structure of a Web Check will vary based upon the authentication requirements of each individual application. Some may only ask you to POST username and password values while others may require the presence of dynamic tokens. In order to identify the specific authentication measures of your application, follow these steps:
The following example shows what information needs to be extracted from the developer tools upon sign-in to your LogicMonitor account, which uses form-based authentication requiring both a Username and Password.
Based on the Developers Tools, we can fill-out the information below:
*as a best practice, passwords should be saved as a property on your devices/websites. As such, you can simply use a token to pull this value from your websites properties.
Jira is an internal ticketing system that uses form-based authentication requiring a Username and Password.
*note that several of the keys do not display any value in the Web Check or developer tools. Some sites, such as Jira, will require you to precisely match the form data in your Web Checks, regardless of whether or not there are any assigned values.
In This Article