---
title: OneSpan Auth Activate Device node
description: The OneSpan Auth Activate Device node prompts for the signature returned by the Digipass authenticator and finalizes the device activation process.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:onespan-activate-device
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/onespan-activate-device.html
keywords: ["Nodes & Trees", "Journeys", "Authentication", "Device Activation"]
page_aliases: ["auth-node-onespan-activate-device.adoc"]
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  troubleshooting: Troubleshooting
---

# OneSpan Auth Activate Device node

The OneSpan Auth Activate Device node prompts for the signature returned by the Digipass authenticator and finalizes the device activation process.

## Example

![onespan user register journey activate device](_images/onespan-user-register-journey-activate-device.png)

This example shows the user registration and device activation journey and highlights the use of the OneSpan Auth Activate Device node:

1. The Username Collector and OneSpan Risk CDDC nodes collect the user's name and device fingerprint data and store them in the shared state.

2. The OneSpan Auth User Register node registers the user.

3. The OneSpan Auth Visual Code node uses the app to obtain a visual authentication code from OneSpan and places it in the shared state.

4. The OneSpan Sample Attributes Collector node collects custom device attributes and stores them in the shared state.

5. The OneSpan Auth Add Device node prompts user for the device code, to compare with the stored device code.

6. Upon successful device code comparison, the process continues to the next OneSpan Auth Visual Code node to get the device signature.

7. The OneSpan Sample Attributes Collector node collects the device signature.

8. The OneSpan Auth Activate Device node prompts the user for the device signature to authenticate the device.

9. When the device is authenticated successfully, the OneSpan Auth Hide Visual Code node stops displaying the visual code and completes the successful authentication.

10. If there's an error at the OneSpan Auth Add Device node or at the OneSpan Auth Activate Device node, the OneSpan Auth Hide Visual Code node is invoked to stop displaying the visual code.

11. The OneSpan Sample Error Display node displays the error message and the authentication fails.

## 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       |
| ------------------ | ---------------------------- | ------------ |
| Registration ID    | As specified in the property | Shared state |
| Digipass signature | As specified in the property | Shared state |

## Dependencies

This node uses the device code and signature values collected by other OneSpan nodes in the journey to activate a device.

## Configuration

This node has no configurable properties.

## Outputs

This node doesn't change the shared state.

## Outcomes

* Success

  The device was successfully activated.

* \`Error

  The device wasn't found in the pending activation list.

## Troubleshooting

Review the log messages and address the issue appropriately.