Record a journey
This guide sets up journey monitoring for an Auth0 tenant and records a journey: a login, a password reset, a sign-up or a custom journey.
You need
Section titled “You need”- The admin role in the workspace.
- An Auth0 tenant connected to the workspace.
- Journeys in the sidebar. It is included from the Max plan, and a platform operator switches it on for the workspace.
- Someone with access to the Auth0 dashboard, to create the probe user.
- About 20 minutes.
For what the feature is and how to read its results, see Synthetic journeys.
Set up monitoring for the tenant
Section titled “Set up monitoring for the tenant”You do this once for each Auth0 tenant.
- Open Journeys.
- Under Not set up yet, choose Set up monitoring beside the tenant. When exactly one tenant needs setup, the same button is also in the page header.
- The dialog Set up journey monitoring opens. Read the Authorisation wording. It has four paragraphs. They say that you are authorised to permit the testing, that Identiguard signs in repeatedly from its own addresses and the sign-ins appear in the tenant log, that the account is a dedicated test account, and that the client is responsible for any approval Auth0 requires.
- Enter the Auth0 database connection. The default is
Username-Password-Authentication. The limit is 128 characters. - Enter Your name. The limit is 200 characters.
- Tick I agree to the authorisation above.
- Choose Set up monitoring. The button is disabled until all three fields are complete.
Create the probe user in Auth0
Section titled “Create the probe user in Auth0”The dialog now reads Create this user in Auth0, with the warning “Copy the password now. It cannot be shown again.”
- Copy the Email. Use this exact address.
- Copy the Password.
- Note the Connection.
- In the Auth0 dashboard, create a user in that connection with that email address and password.
- Back in Identiguard, choose I have created the user.
The tenant now has its own card on the Journeys page, with “No journeys recorded yet.”
Give the probe user access to the application you want to test, and nothing else.
The five wizard steps
Section titled “The five wizard steps”On the tenant card, choose Record a journey. The wizard has five steps, listed on the left: Journey type, Details, Record, Review, Test and switch on.
1. Journey type
Section titled “1. Journey type”- Choose the tenant under Choose a tenant. Only Auth0 tenants with monitoring set up are listed.
- Choose one type: Login, Password reset, Sign-up or Custom. Each card shows three facts, under Schedule, Password and Address.
- Choose Continue.
The diagram “A typical (type) journey” is an outline only. Your recording decides the real steps.
You cannot change the type after the journey is saved.
2. Details
Section titled “2. Details”| Field | Rules |
|---|---|
| Journey name | Up to 80 characters, for example “Web login”. You cannot rename a journey later. |
| Start URL | Must be an https address on a public host. Use a page a signed-out user can open. You cannot change it later. |
| Allowed hosts | The only places a replay may go. The start URL’s host is always allowed. Add each other host the journey passes through, such as the Auth0 domain or a custom domain, with Add host. If you paste a full URL, only its host is kept. A journey can have at most 8 hosts. |
| How often should it run? | Every 5 minutes, Every 10 minutes, Every 15 minutes, Every 20 minutes, Every 30 minutes, Hourly, Daily or Weekly. A sign-up journey offers Hourly, Daily and Weekly only. The default is every 5 minutes. |
| Run from | EU, US or both. At least one must stay ticked. The default is EU only. |
Choose Continue. If it is disabled, the reason is shown beside it.
3. Record
Section titled “3. Record”- Choose Start recording. A real browser opens inside the page.
- Walk through the journey exactly as a customer would, using the probe user.
- Use the panel Help the recording when the journey needs a code, an emailed link or MFA (see the table below).
- When the journey has reached the page that proves success, choose I have finished. Identiguard closes the browser and turns what you did into steps.
| Control | When to use it |
|---|---|
| Fill code | On an Auth0 code screen. Identiguard types the current authenticator code or the emailed code for you. Then press Continue in the recorded browser. |
| Open the emailed link | Shown for Password reset and Sign-up journeys only. Opens the reset or verification link from the probe’s mailbox in the recorded browser. |
| Add MFA step | For an MFA screen you could not complete in the recorder. The step is added after the sign-in, and you can move it in Review. |
| Passkey ready | A badge, not a button. The recorded browser answers passkey and security key prompts with its own built-in key. Saving the journey keeps it as the probe’s passkey. |
Limits while recording:
| Limit | Value |
|---|---|
| Session length | 15 minutes. A countdown shows the time left and turns red under 2 minutes. |
| Idle time | 10 minutes without interaction ends the session |
| Open sessions | One for each tenant, one for each person, two for each workspace |
| Starts | 12 for each workspace in an hour |
A shared pool of recording browsers also serves all customers, so at busy times no browser may be free.
If you leave the page during a recording, Identiguard asks “Leave and end this recording?”. Choose Stay to continue.
4. Review
Section titled “4. Review”The review shows the heading “N steps · N need checking”, a flow chart, and the step editor What Identiguard will replay. See The step editor for every control.
Before you can save:
- Fix every step with the Check this badge.
- Make sure there is at least one Assertion step. A check is what lets a journey fail when the application does not load. Add one with Add a check.
- Clear every item under This journey cannot be saved yet.
Then choose Save journey. You see “Journey saved. It stays off until a test run passes.” Discard throws the recording away.
5. Test and switch on
Section titled “5. Test and switch on”A journey stays off until one test run passes. See Run a test, then start running.
Record a login journey
Section titled “Record a login journey”- On the tenant card, choose Record a journey.
- Choose the tenant and Login, then Continue.
- Complete Details and choose Continue.
- Choose Start recording.
- In the recorded browser, sign in with the probe user’s email address and password.
- If Auth0 asks for a code, choose Fill code, then press Continue in the browser. See Record a journey with MFA.
- Wait until the application has loaded, then choose I have finished.
- In Review, fix any Check this steps and make sure there is an Assertion, for example text that appears only when the user is signed in.
- Choose Save journey, then test it.
A login journey has no Open the emailed link button.
Record a password reset journey
Section titled “Record a password reset journey”Each run sets a new password, and Identiguard keeps it for the next run.
- On the tenant card, choose Record a journey.
- Choose the tenant and Password reset, then Continue.
- Complete Details. Add any extra Allowed hosts, for example the Auth0 custom domain. Choose Continue.
- Choose Start recording.
- In the recorded browser, request a password reset for the probe address.
- Choose Open the emailed link. You see “Opened in the recorded browser.”
- Set a new password in the page.
- If Auth0 asks for a code, choose Fill code, then press Continue in the browser.
- When the success page shows, choose I have finished.
- In Review, fix any Check this steps and make sure there is at least one Assertion.
- Choose Save journey, then test it.
Record a sign-up journey
Section titled “Record a sign-up journey”The wizard calls this type Sign-up. The journey row calls it Registration.
- On the tenant card, choose Record a journey.
- Choose the tenant and Sign-up. Note the address under Register with this address. It is not the probe’s normal address. Choose Continue.
- Complete Details. Only Hourly, Daily and Weekly are offered. Choose Continue.
- Choose Start recording. The address under Register with this address is shown again on this step.
- In the recorded browser, register with that exact address and the probe password.
- If Auth0 sends a verification email, choose Open the emailed link.
- When the application or the success page shows, choose I have finished.
- In Review, fix any Check this steps and make sure there is at least one Assertion.
- Choose Save journey, then test it.
On each later run Identiguard registers a fresh address, because an address can sign up only once.
Record a custom journey
Section titled “Record a custom journey”Use Custom for any other journey you can walk through in a browser, for example opening a profile page after sign-in.
- On the tenant card, choose Record a journey.
- Choose the tenant and Custom, then Continue.
- Complete Details. Add every host the journey visits to Allowed hosts. Choose Continue.
- Choose Start recording and walk through the journey with the probe user.
- Choose I have finished.
- In Review, check each step and add an Assertion for the final page.
- Choose Save journey, then test it.
A custom journey uses the same probe address every run, and types the probe password wherever you typed it. It has no Open the emailed link button.
Record a journey with MFA
Section titled “Record a journey with MFA”The probe supports TOTP (authenticator app), email code, passkey or security key, and recovery code. Push notification and SMS are not in the supported list.
- Start recording as usual and sign in with the probe user.
- For an authenticator app enrolment screen, choose “Trouble Scanning?” in the Auth0 page so that the secret is shown as text. Then choose Fill code and press Continue in the browser.
- For an email code, choose Fill code and press Continue in the browser.
- For a passkey or security key, complete the prompt in the page and wait for the Passkey ready badge.
- If you cannot complete an MFA screen in the recorder, choose Add MFA step.
- In Review, open the Complete MFA step and set Method: Auto, TOTP, Email code, Passkey or security key or Recovery code. Move the step with the arrows if it is in the wrong place.
- Save and test the journey.
The step editor
Section titled “The step editor”The step editor appears in the wizard’s Review step and on the Edit steps page.
- Flow chart. One node for each step. Choose a node to select its step.
- “N steps · N need checking”. The link jumps to the first flagged step.
- Each step has a number, a name and a sentence that says what Identiguard does, for example “Open (URL)”, “Type into textbox “Email”“, “Press Enter”, “Wait for the text “…”“, “Open the password reset link from the probe mailbox” or “Complete MFA”.
- Badges. Assertion marks a check. Check this marks a step the recorder was not sure about.
- Move up, Move down, Delete on each step.
| Control | What it does |
|---|---|
| Value for this step | For a step that types text. The recording hides what you typed, so you supply it here. Type a fixed value, or choose a chip: {{identity.email}} (the probe address), {{identity.password}} (the probe password) or {{identity.newPassword}} (the new password in a reset). |
| Add Enter key press | On a step that types text. Adds a step that presses Enter in that field. |
| Add MFA step | On a click or key press step. Adds a Complete MFA step. A journey can have one MFA step. |
| Method | On the MFA step: Auto, TOTP, Email code, Passkey or security key, Recovery code. |
| Add a check | Adds an assertion. Choose Text appears and Add text check, or URL starts with and Add URL check. A URL check also adds that site to the allowed hosts. |
Journey settings holds How often should it run?, Run from, MFA method (read only: change it on the MFA step) and Allowed hosts. A host that a step still uses cannot be removed.
Limits:
| Limit | Value |
|---|---|
| Steps in a journey | 40 |
| Checks | At least one |
| MFA steps | One |
| Allowed hosts | 8 |
| Time for one run | 60 seconds, or 120 seconds with an MFA step |
Run a test, then start running
Section titled “Run a test, then start running”The step Test and switch on reads “A journey stays off until one test run passes. The run replays it once from a probe host, against your live sign-in page.”
- Choose Run a test. You see “Queueing a test run.” and then “Waiting for a probe to replay the journey. This usually takes under a minute.”
- Wait for the result.
- The test run passed: “Every step replayed. Start running it on its schedule when you are ready.”
- The test run did not pass: the panel names the reason and the step, and the chart highlights the failing step. Choose Back to review, fix the step, save, and choose Run the test again.
- Choose Start running. You see “Journey running.” and return to the Journeys page.
Notes:
- Nothing runs until you choose Run a test, and a pass does not start the schedule. You must choose Start running.
- If no result arrives within 5 minutes you see “No result yet. The run stays queued, and its result will show on the Journeys page.”
- Done for now leaves the journey saved under Awaiting first pass. To finish later, see Manage journeys.
- A run that started before your last change to the steps does not count as a pass.
What you should see
Section titled “What you should see”The journey is listed on the tenant card under Running, first with Queued or Not run yet and then with Passing. It has a lane in the Live journey map.
If it does not work
Section titled “If it does not work”Setting up monitoring
Section titled “Setting up monitoring”| What you see | Why | What to do |
|---|---|---|
| “No tenant is set up for journeys yet” | You opened the wizard before any tenant was set up | Choose Go to Journeys, then Set up monitoring |
| “Could not set up journey monitoring” with “The authorisation wording has changed. Reload and read it again.” | The wording changed while the dialog was open | Reload the page, read it and agree again |
| “Journey monitoring is already set up for this tenant.” | Someone set it up in another tab | Reload the page |
| “The probe mailbox domain is not configured on this deployment.”, “Could not secure the probe credentials.” or “This tenant has no encryption key and cannot store probe credentials.” | A platform problem | Escalate to the product team |
| “Close without copying the password?” with “It cannot be shown again. Reissue it from the tenant’s menu if you lose it.” | You are closing the credentials screen | Copy the password first. Close anyway closes the dialog. If you lost the password, use Reissue probe credentials. |
| “Select and copy the password manually” | The browser blocked access to the clipboard | Select the text in the field and copy it by hand |
Details and allowed hosts
Section titled “Details and allowed hosts”| What you see | Why | What to do |
|---|---|---|
| “Give the journey a name”, “Enter the start URL” or “The start URL must be an https address” | Details is not complete | Complete the field. An http address is refused. |
| “Enter a host name.” or “A host is lowercase letters, digits, dots and hyphens.” | The host is empty or not valid | Enter a host name only, such as login.example.com |
| “(host) is not a public host name.” | IP addresses and internal names are refused | Enter a public DNS name |
| “(host) is already allowed.” | The host is already in the list | Nothing to do |
| “A journey may allow at most 8 hosts.” | The limit is reached | Remove a host you do not use |
Starting and running the recorder
Section titled “Starting and running the recorder”| What you see | Why | What to do |
|---|---|---|
| “No recording browser is free” with “All recording browsers are in use. Try again in a few minutes.” | The shared pool of browsers is full | Wait, then choose Try again |
| “You already have a recording session open. Finish or discard it, then try again.” | One session for each person | Finish or cancel your other recording or tab |
| “Your workspace already has the most recording sessions it can have open at once. Finish or discard one, then try again.” | Two sessions for each workspace | Wait for a colleague to finish |
| “Your workspace has started a lot of recording sessions in the last hour. Try again later.” | 12 starts in an hour for each workspace | Wait |
| “A session is already open for this tenant”, and nothing has driven it since | An old session was left open | Choose Discard it and start recording. This is safe. |
| “A session is already open for this tenant”, and it is still being driven, probably in another tab | Someone is recording on this tenant now | Check with your colleagues first. Discard it and start recording ends their recording. |
| “Could not start a browser session. Try again in a moment.”, “The browser session started but produced no Live View URL.” or “Teaching is not configured on this deployment.” | The browser did not start | Try again. Escalate if it continues. |
| “The teaching session timed out. Start again when you are ready.” | The 15-minute limit was reached | Prepare the test account first, then record again |
| “Ten minutes without interaction ends the session. Keep going, or cancel and record again.” | Idle warning | Interact with the browser, or finish |
| “The recorded browser has closed: (reason).” | The browser was closed for inactivity, crashed, or the connection was lost | Start recording again |
| “Leave and end this recording?” or “Leave without saving this journey?” | You are leaving with work in progress | Stay keeps it. Leave discards it. |
Codes, emailed links and MFA
Section titled “Codes, emailed links and MFA”| What you see | Why | What to do |
|---|---|---|
| “The browser above is not on an Auth0 code screen.” | You chose Fill code on the wrong page | Go to the MFA code screen first |
| “Could not read the secret on this screen. Choose “Trouble Scanning?” in the browser above, then try again.” | The enrolment screen shows only a QR code | Choose “Trouble Scanning?” in the Auth0 page, then Fill code |
| “No code has arrived yet. Try again in a few seconds.” | The email code is not yet in the probe mailbox | Wait and try again |
| “The probe user already has an authenticator in Auth0. Reset MFA for it in the Auth0 dashboard, then start again.” | The probe user was enrolled outside Identiguard | Reset the user’s MFA in Auth0, use Reset MFA in the tenant menu, then record again |
| “No email has arrived yet. Request it in the browser above, then try again.” | You chose Open the emailed link before the email arrived, or before you requested it | Request the reset or verification in the recorded browser, wait, and try again |
| “Could not reach the recorded browser.” or “Could not open that link in the recorded browser.” | The browser cannot be reached | Try again. If it continues, cancel and record again. |
Finishing the recording
Section titled “Finishing the recording”| What you see | Why | What to do |
|---|---|---|
| “The recording is on its way” with “The recording is not ready yet. Try again in a few seconds.” or “Could not reach the recording just now. Try again in a few seconds.” | The recording is still being prepared | Choose Try again |
| “Could not turn that recording into a journey.” | The recording is empty or cannot be used | Record again, and interact with the page |
| “This teaching session has already ended. Start a new recording to teach this journey.” | You chose I have finished on a closed session | Start a new recording |
| “This recording has already been turned into a journey.” | The recording was already processed | Continue in Review |
Review and save
Section titled “Review and save”| What you see | Why | What to do |
|---|---|---|
| “N need checking”, or the badge Check this | The recorder flagged a step | Open the step and read its warning |
| “(field) was filled with N characters, which the recording masks. Supply a value or remove the step.” | The typed value was hidden and is not a known probe value | Type the value, or choose a chip |
| “(field) is a dropdown. The option chosen is masked in the recording, so it must be supplied before this flow is enabled.” | The chosen option was hidden | Enter the option’s value |
| “The submit was inferred as Enter. Check it in the review step.” | No click on the submit button was recorded | Confirm the step. Or delete it and use Add Enter key press on the right field. |
| “(element) has no accessible name” or “(element) has no role this recipe can express” | The element cannot be found reliably | Delete the step, or record again using a labelled control |
| “Add a check in the review step, such as text that appears when the journey has succeeded.”, or “Add a check that the journey succeeded” | The journey has no assertion | Add a check, then a text or URL check |
| “Give the empty check a text or a URL” | A check is empty | Complete the check or delete it |
| “Remove one of the two MFA steps in a row” | Two MFA steps | Delete one |
| “Two steps are named X” | Duplicate step names | Delete one of them |
| “Replace the unknown placeholder in a value” | A value contains a {{...}} name that does not exist |
Use one of the chips |
| “Fix a URL the journey visits” | A URL is not https, or its host is not allowed |
Add the host to Allowed hosts, or use https |
| This journey cannot be saved yet | The list of problems above | Clear each item |
| “Cannot be removed: used by the start URL, step X.” | A step still visits the host | Delete or change that step first |
| “Teaching enrolled an MFA factor on the probe user, and Identiguard kept none of it. Reset MFA for the probe user in the Auth0 dashboard before the test run, so the probe can enrol its own.” A similar message appears after saving. | MFA was enrolled during the recording with a device Identiguard does not hold | Reset the probe user’s MFA in Auth0 before you run the test |
| “Could not save the journey.” | The server refused the steps, a host that is not public, or a schedule too frequent for the type | Fix what the message names |
Testing
Section titled “Testing”| What you see | Why | What to do |
|---|---|---|
| “The test run could not be queued. Try again in a moment.” or “The test run could not be queued (NNN).” | The request failed | Try again |
| “This journey already has a run in flight.” | A run is already queued or running | Wait for it |
| “No result yet. The run stays queued, and its result will show on the Journeys page.” | No result within 5 minutes | Check the Journeys page later. If the run shows No probe runner available, escalate. |
| The test run did not pass, with a reason | See the run results in Synthetic journeys | Fix the highlighted step in Review, then Run the test again |
| “Could not switch the journey on” | The journey has not passed a test | Run a test that passes first |