Settings: Bypass a login wall

Once you register a license, accessFlow automatically audits your website for compliance issues. However, sometimes you will need to set up certain parameters to enable auditing your site.

If your website requires a login, provide a list of the actions that our audit should take in order to log in and audit your site. List the steps in the order that they should be performed.

Watch the video to learn how to record a bypass for login walls using our browser extension. Recording a bypass for login walls is supported on Google Chrome and Microsoft Edge.

You can also manually add the login steps required for your website.

To add login steps manually

1. Go to Settings and select Site Access Settings.

2. Under Steps to bypass login walls select Add Manually.

3. Under Login Page Path enter the the relative webpage. For example, /login

4. Select an Action type. The action type is a step that must be performed to login to your website.

• Click an element
• Check a checkbox
• Set an input value
• Type text
• Type password
• Wait 10 seconds
• Wait for selector
• Press keys

5. Enter the Action selector. To get the selector, right-click on an element in the web page, select Inspect and copy the selector. For example, #email-button

6. Select Add Step to add another step in the login process.

7. Add this final step after your login steps to confirm that the login wall bypass worked:

• Select Add Step and select the action type Click an element and then select any element on the page that appears after login to verify that login was complete. For example, select the user profile name. 
• Change the action type to Wait for selector.

8. Select Save & Validate Steps.

Each step is executed and validated. If there are errors, select the down arrow next to the error message to view the errors. Fix the errors and select Save & Validate Steps again.

Tips:

• If you log in using an SSO provider, whitelist our IP address if bot protection is enabled. Contact support for details.
• If you get an error that a selector doesn't exist, this may be caused by dynamic HTML where the classes and ids change. A developer familiar with selectors should choose a more flexible selector that will find the element more consistently.
• If you use two-factor authentication, our audit can't access your site. To resolve this, set a cookie header in Dashboard > Audit Settings > Basic audit settings. Make sure the cookie has an extended expiration to prevent timeouts. Otherwise you'll need to update the session cookie regularly.