---
title: OneSpan Get User Authenticator node
description: The OneSpan Get User Authenticator node retrieves the authenticators assigned to a user and helps in appropriately enabling the user's authentication and security levels.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:onespan-get-user-authenticator
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/onespan-get-user-authenticator.html
keywords: ["OneSpan", "Authenticator"]
page_aliases: ["auth-node-onespan-get-user-authenticator.adoc"]
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  troubleshooting: Troubleshooting
---

# OneSpan Get User Authenticator node

The OneSpan Get User Authenticator node retrieves the authenticators assigned to a user and helps in appropriately enabling the user's authentication and security levels.

## Example

This example journey shows user registration and login. It highlights the use of the OneSpan Get User Authenticator node:

![onespan get user auth journey](_images/onespan-get-user-auth-journey.png)

The OneSpan Get User Authenticator node gets the authenticators assigned to a user and appropriately directs the flow in the journey:

| Outcome | Description                                                                                                                                                                         |
| ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `TYP`   | The flow is directed to the Message node.                                                                                                                                           |
| `VR10`  | The flow is directed to the OneSpan Auth Generate VOTP node.                                                                                                                        |
| `Both`  | The flow is directed to the Choice Collector node. The Choice Collector node forwards the flow to the OneSpan Auth Generate VOTP node or the Message node based on the choice made. |
| `None`  | The flow is directed to Register Authenticator node so the user can be assigned an authenticator.                                                                                   |

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

This node requires the following inbound data:

| Description | Attribute name               | Source       |
| ----------- | ---------------------------- | ------------ |
| Username    | As specified in the property | Shared state |

## Dependencies

To use this node, you must integrate OneSpan in your PingOne Advanced Identity Cloud tenant environment and enable authentication through a OneSpan VIR10 authenticator.

## Configuration

The configurable properties for this node are:

| Property                 | Usage                                                                                                                        |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| IAA Domain               | The domain in which the user account resides. In a sandbox, the domain is the same as your tenant name. For example, master. |
| User Name In SharedState | The key parameter in shared state that represents the OneSpan IAA username. For example, username.                           |

## Outputs

This node doesn't change the shared state.

## Outcomes

The outcome specifies the authenticator configured:

* `TYP`

  A `TYP` authenticator is configured.

* `VIR10`

  A `VIR10` authenticator is configured.

* `Both`

  Both `TYP` and `VIR10` are configured.

* `None`

  No authenticator is configured.

## Troubleshooting

If this node logs an error, review the log messages for the transaction to find the reason for the exception and address the issue appropriately.