What Is the Difference Between Site Login and HTTP Authentication?
What Is the Difference Between Site Login and HTTP Authentication?
Read on to learn the difference between HTTP authentication and Form-based authentication, and a tool that can help to configure these protocols.
Join the DZone community and get the full member experience.
Join For FreeDiscover how to provide active runtime protection for your web applications from known and unknown vulnerabilities including Remote Code Execution Attacks.
When configuring a target, you sometimes need to configure login details to the web application. This allows Acunetix to check the restricted areas in your web application. There are two types of authentication that can be done with a website – Form-based authentication and HTTP Authentication.
Form-based authentication is the most popular form of authentication. It is the type of authentication which is implemented in the web application and is used in popular websites such as Gmail or Facebook.
This type of authentication can be configured in Acunetix from the Site Login section of a Target.
On the other hand, HTTP Authentication is configured in the Web Server and is often used as an added level of security. The authentication window appears before any page is loaded, and looks like what is shown in the screenshot. Different browsers display this message differently.
HTTP Authentication is also supported by Acunetix and can be configured from the Target’s settings > HTTP tab > HTTP Authentication.
Find out how Waratek’s award-winning application security platform can improve the security of your new and legacy applications and platforms with no false positives, code changes or slowing your application.
Like This Article? Read More From DZone
Published at DZone with permission of Nicholas Sciberras , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}