Healthcare - CSR Help Desk - Verify User Magic Link Authentication - Subflow

The Healthcare - CSR Help Desk - Verify User Magic Link Authentication - Subflow lets existing users authenticate using a link sent to the email address that’s associated with their account.

Purpose

The Healthcare - CSR Help Desk - Verify User Magic Link Authentication - Subflow presents users with the option to send a magic link to the email address associated with their account. After the link is sent, the flow checks the status of the link.

If the user clicks the link, the flow authenticates the user.
If the link expires, the flow presents an error message. The magic link expires after 2.5 minutes (150 seconds).

Structure

This flow is divided into sections using teleport nodes:

Display Magic Link Form: Uses a PingOne node to look up the user, then presents an HTML form from which the user can send a magic link. If the user clicks Submit, the flow simultaneously progresses to the Create Challenge and Send Email and Challenge Acceptance By The User sections. If the user clicks Cancel, the flow progresses to the Return Success section.
Create Challenge and Send Email: Uses a flow conductor to begin an out-of-band process, then uses a PingOne node to send a magic link email. The flow then progresses to the Display Magic Link Polling And Check For Challenge Status section.
Challenge Acceptance By The User: Checks the challenge status. If the challenge is not expired, the flow displays a UI holding screen, then invokes the Healthcare - CSR Help Desk - Device Authentication - Subflow. When the subflow completes, the challenge status is set to approved and a success message displays for the user. If the challenge expires, an error message displays.
Display Magic Link Polling And Check For Challenge Status: Displays a custom HTML template directing users to click the magic link. When the challenge is approved, the flow progresses to the Go To Success section. If the challenge expires, the flow progresses to the Challenge Expiration section.
Go To Success: Progresses to the Return Success section.
Challenge Expiration: Denies the challenge if the magic link expires. The flow then progresses to the Return Error section.
Return Success: Sends a success JSON response, indicating that the flow completed successfully.
Return Error: Uses a function node to enrich the error details, then sends an error JSON response indicating that the flow completed unsuccessfully.

Input schema

This flow has the following inputs:

Input name Required Description

Input name	Required	Description
`p1UserId`	Yes	The current user’s PingOne user ID.
`canChangeDevice`	Yes	Indicates whether the user can change MFA devices.
`p1MFAPolicyId`	No	The PingOne MFA policy to apply.
`allowedDeviceTypes`	No	A string containing any or all of `SMS, EMAIL, FIDO2, TOTP, VOICE, MOBILE` indicating the allowed device types.
`companyLogo`	No	The company logo. Used only when the main flow was launched using a redirect.

p1UserId

Yes

The current user’s PingOne user ID.

canChangeDevice

Yes

Indicates whether the user can change MFA devices.

p1MFAPolicyId

The PingOne MFA policy to apply.

allowedDeviceTypes

A string containing any or all of SMS, EMAIL, FIDO2, TOTP, VOICE, MOBILE indicating the allowed device types.

companyLogo

The company logo.

Used only when the main flow was launched using a redirect.

Output schema

This flow has the following outputs:

Output name Description

Output name	Description
`subflowResult`	The result status of the flow.
`errorMessage`	The error message to display in the parent flow.
`errorDetails`	The details of the error that occurred in this flow.

subflowResult

The result status of the flow.

errorMessage

The error message to display in the parent flow.

errorDetails

The details of the error that occurred in this flow.

Variables and parameters

This flow does not directly use any variable or parameter values.

PingOne Solution Packs