---
title: Secret Double Octopus (SDO) nodes
description: Integrates with Secret Double Octopus (SDO) to provide high-assurance, passwordless authentication system engineered to address the diverse authentication needs of a real-world, working enterprise.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:secret-double-octopus
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/secret-double-octopus.html
page_aliases: ["auth-node-sdo-about.adoc"]
section_ids:
  auth-node-sdo-prereq: SDO prerequisites
  auth-node-sdo-setup: Setting up
  octopus-node: Octopus node configuration
  outcomes: Outcomes
  configuration: Configuration
  octopus-return-node: Octopus Return node configuration
  outcomes_2: Outcomes
  configuration_2: Configuration
---

# Secret Double Octopus (SDO) nodes

Integrates with [Secret Double Octopus (SDO)](https://doubleoctopus.com/solutions/passwordless-mfa/) to provide high-assurance, passwordless authentication system engineered to address the diverse authentication needs of a real-world, working enterprise.

## SDO prerequisites

Before configuring the SDO nodes in PingOne Advanced Identity Cloud, you complete the following prerequisite steps using the Octopus Management Console:

* [Integrate your corporate directory](https://support.doubleoctopus.com/support/solutions/articles/33000278687).

* [Create a REST API service](https://support.doubleoctopus.com/support/solutions/articles/33000277485#UUID-f3ed3105-4406-d91e-96f9-61d0ac65a5e2).

After the prerequisite configurations are completed, you can obtain the API token, service URL, and service certificate from the Octopus Admin console. These three values are essential to configure SDO nodes in PingOne Advanced Identity Cloud.

## Setting up

To set up SDO with PingOne Advanced Identity Cloud, configure [Octopus node](#octopus-node) and [Octopus return node](#octopus-return-node).

A typical authentication journey using SDO nodes:

![sdo journey](_images/sdo-journey.png)

### Octopus node configuration

The Octopus node sends the Octopus authentication request.

#### Outcomes

* `True`

  Successfully obtained device ID.

* `Error`

  An error occurred when obtaining device ID.

#### Configuration

| Property    | Usage                                                                                   |
| ----------- | --------------------------------------------------------------------------------------- |
| API token   | The API Token of the Octopus Authenticator REST service from the Octopus Admin console. |
| Service URL | The URL of the Octopus Authenticator REST service from the Octopus Admin console.       |
| Message     | The message to be sent on authentication by push.                                       |

### Octopus Return node configuration

The Octopus Return node checks that the Octopus authentication request was successfully approved.

#### Outcomes

* `True`

  Successfully verified the device.

* `False`

  The device cannot be verified.

* `Unregistered`

  The device is not registered yet.

* `Error`

  An error occurred during verification.

#### Configuration

| Property            | Usage                                                                                     |
| ------------------- | ----------------------------------------------------------------------------------------- |
| Service Certificate | The certificate of the Octopus Authenticator REST service from the Octopus Admin console. |