Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

HTTP Form Login Monitor

I'm trying to get the form monitor working against a web app of ours and not having a lot of joy. Has anyone run into/overcome similar? Settings are as follows (overridden from template):

Login Form Keywords: (login)
Login Control Keywords: (email)
Password Control Keywords: (password)

When I test this, it fails with the error message:

Login form name = login has only 1 inputs. At least 2 expected.
Page contains 1 form(s). Form 'login' inputs: ('camefrom' 'email' 'password' );
Assumed form with name = login as login form

The error message might be a little clearer. The login form has only 1 input - it then goes on to list the 3 inputs it has. Does this mean that its not matched the user/pass fields? Is there any way to get a more helpful error message rather then blindly change things and hit refresh?

Thanks!

Find more posts tagged with

http_form_template

sam

Accepted answers

All comments

aLTeReGo

The message is stating that a single forum was found on the page called "login", which has three inputs, 'camefrom' 'email' and 'password'. Without seeing the page source for the page being monitored it's difficult to provide more information. Such as, what is 'camefrom', and is it required?

thefish

"camefrom" is a hidden field that contains the path before being forwarded to login. "email" and "password" as specified in the controls section of the monitor are what I need. They are all being detected, yet the monitor complains of only 1 field available.

aLTeReGo

How is the "camefrom" field populated? Again, without looking at the page source it's very difficult to understand how the form is constructed, or how input is handled. If the form relies on JavaScript to function then it will not work with SAM's HTTP Form Login Monitor, as the Form Login Monitor does not possess a JavaScript engine to execute javascript functions.

To determine if JavaScript is the issue, disable JavaScript in your web browser, verify it by going to this site, and then attempt to login to the website or web application that you're attempting to monitor with SAM's Form Login Monitor.