Sometimes just the username and password fields are not enough to authenticate to a site. Some sites requires some custom fields or even the "submit" button in order to successfully authenticate you. So you may have to add them as custom fields in the Aspider Configuration.
You can also open the browser inspect mode in order to break down the authentication request and make sure you are not missing any field.
Don't worry about those hidden fields inside the form, Aspider will automatically include them in the request, you don't have to do anything.
Watch out for "logout" pages which usually send requests to the browsers to clear their cookies. If Aspider is requested to clear its cookies for logging out, it will do that and will not try to re-login.
Suggestion: Add an exclusion pattern for the "log out" pages.
Unfortunately not at the moment, Aspider Cookie Based Authentication is built to send only one request, but we are already considering improvements for it.
If your login form relies on javascript for sending the Authentication request your form element probably won't have an "action" attribute, which Aspider use for sending the POST request to. So you wouldn't be able to authenticate.
As of Java 8, Aspider supports and has been tested to work on the following protocols:
Note: SSLv2 and SSLv3 are not supported by Aspider.