---
title: TypingDNA Reset Profile node
description: Use the TypingDNA Reset Profile node to reset an end user's TypingDNA profile. When a user's profile is reset, all the patterns recorded for the user are deleted, and the user is enrolled again the next time they sign on. To reset a profile, you must use the same API key, API secret, and the salt as configured in the TypingDNA Decision node.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:tdna-reset-profile
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/tdna-reset-profile.html
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  troubleshooting: Troubleshooting
---

# TypingDNA Reset Profile node

Use the TypingDNA Reset Profile node to reset an end user's TypingDNA profile. When a user's profile is reset, all the patterns recorded for the user are deleted, and the user is enrolled again the next time they sign on. To reset a profile, you must use the same API key, API secret, and the salt as configured in the TypingDNA Decision node.

## Availability

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

## Inputs

This node reads the `username` of the authenticating user from the shared state.

Implement a [Platform Username node](../platform-username.html) earlier in the journey.

## Dependencies

[The dependencies for TypingDNA nodes are explained here.](tdna-set.html#tdna-depend)

## Configuration

| Property           | Usage                                                                                                                                                                                                            |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API URL            | The URL for TypingDNA API, for example, https\://api.typingdna.com.                                                                                                                                              |
| API key            | The API key from your TypingDNA account.                                                                                                                                                                         |
| API secret         | The API secret from your TypingDNA account.                                                                                                                                                                      |
| Hash algorithm     | The hashing algorithm that is used for anonymizing usernames before sending them to the TypingDNA Authentication API.                                                                                            |
| Salt               | A string that is used to anonymize the user ID for additional security. For example, username or user email.Default is null.                                                                                     |
| Request identifier | An optional parameter that can be used to identify requests coming from a specific PingOne Advanced Identity Cloud authentication journey. The identifier also appears in the TypingDNA logs.Default: ForgeRock. |
| Request time out   | Time in milliseconds after which requests to the TypingDNA Authentication API time out if no response is received.Default: 8000 ms                                                                               |

## Outputs

This node doesn't change the shared state.

## Outcomes

* `Success`

  This outcome is achieved when the profile was successfully deleted.

* `Error`

  This outcome is achieved when a critical error occurs, such as if invalid API credentials are entered. You can link this outcome to an alternative node, such as a `Retry Limit Decision node`, or to the Failure node.

## Troubleshooting

If this node logged an error, review the transaction log to find the reason for the error.