open|awsvpn

Demo & Review Guide

This page is for QA engineers, app-store reviewers, and testers who need to exercise the full openlawsvpn SAML authentication flow without a production account. Download the sample config below, follow the steps, and the app will walk you through the rest.

Sample client config

saml-client.ovpn

OpenVPN profile · SAML flow · demo.openlawsvpn.com:4433

Download

How to connect

1 Download saml-client.ovpn using the button above.
2 Open the openlawsvpn app on your device. On iPhone or iPad, tap + Add Profile and pick the file from Files; on Android, tap Import .ovpn File; on desktop, use Import profile. Select the downloaded .ovpn file.
3 Tap Connect. The app will open a browser window pointing to the demo login page. Enter the credentials shown in the box below. On iOS, the first time you connect, iOS asks "openlawsvpn Wants to Use openlawsvpn.com to Sign In" — tap Continue.
4 Click "Connect" on the login page. The browser window closes automatically and the VPN tunnel comes up. On iOS you may first see "This form is not secure — Submit?" — tap Submit; this returns the sign-in token to the app over its private loopback address.
5 Verify the connection — the app status bar should show Connected and a server address of demo.openlawsvpn.com.

Demo credentials

Username reviewer

Password Demo2026!

Note for app-store reviewers: This is a read-only sandbox environment. No real user data is stored. The demo server accepts only the credentials above and rejects everything else. The VPN tunnel terminates on a dedicated review instance and carries no production traffic.

iOS reviewers — two expected system prompts: (1) The first time you tap Connect, iOS asks "openlawsvpn Wants to Use openlawsvpn.com to Sign In" — tap Continue. (2) After entering the credentials and tapping Connect on the login page, iOS may show "This form is not secure — Submit?" — tap Submit. Both are standard iOS prompts; the sign-in token is delivered to the app over its private loopback address (127.0.0.1) and nothing leaves the device.

Desktop browser only — "wants to access other apps" prompt: When testing this page directly in a desktop browser, you may see a permission dialog after clicking Connect. This is the browser asking whether a script can close the tab — click Allow. This prompt does not appear in the actual app flow, where the login page runs inside an in-app browser that the app itself controls and closes.