Site Authentication
Introduction
When adding a new site to your AAArdvark Workspace, you might need to configure authentication settings to access protected pages. Don’t worry—you can always update these settings later if needed.
To get started, go to your dashboard and click Add a New Site at the top of the page.
Setting up Site Authentication
AAArdvark allows you to log in before scanning, making it possible to test restricted or members-only content.
You can configure authentication settings for specific pages or apply them site-wide, depending on your needs.
Authentication Methods
AAArdvark offers three authentication methods: HTTP Basic, Login Form, and Custom Header.
HTTP Basic:
This method is often used for development sites that require a login for privacy. Just enter your username, password, and a test URL to verify the credentials.
Login Form:
For sites with a standard login screen, AAArdvark supports cookie-based authentication.
Custom Header:
If your site uses custom headers for authentication, select this option.
AAArdvark currently supports Cookie Authentication for WordPress, Drupal, and Laravel. If you’d like to see support for another platform, submit a feature request.
To set up this method:
- Site Type:
Select the platform your site is built on, then enter your username and password. - Username/Password:
AAArdvark stores your credentials securely using strong encryption. For added security, we recommend creating a dedicated user account with limited permissions for accessibility scanning.
Custom Login Pages
For Laravel sites with a custom login page, you may need to update the username, password, and submit button selectors to ensure proper functionality.
AAArdvark does not support custom login pages for WordPress and Drupal sites.
