---
title: "Hardened Hashing Password Transformer Plugin"
description: "A password transformer plugin that provides additional hashing algorithms for storing passwords."
url: "https://curity.io/resources/learn/hardened-hashing-plugin/"
date: "2026-11-19"
area: "tutorials"
topic: "code-examples"
pagegroup: "plugins-password-transformers"
repository: "https://github.com/curityio/hardened-hashing-plugin"
---

# Hardened Hashing Password Transformer Plugin

For security reasons you should never store passwords in a plain-text format. To protect them, you should transform passwords with a key derivation function or hash algorithm. The Curity Identity Server supports [a number of popular password transformation algorithms](https://curity.io/docs/identity-server/facilities/credential-managers#transformation-algorithms), and allows implementing others through Password Transformer plugins.

This plugin adds support for the Argon2 family of hashing algorithms (argon2id, argon2i, argon2d, defined in [RFC 9106](https://www.rfc-editor.org/rfc/rfc9106.html)) as well as the scrypt algorithm (defined in [RFC 7914](https://www.rfc-editor.org/rfc/rfc7914.html)). The argon2id algorithm is one of the algorithms that [OWASP recommends](https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html) for hashing passwords. Using the strongest algorithms provides robust protection against brute-force attacks that try to reverse the password value from a hash the attacker manages to obtain.

The Plugin Has Production-level Support

Curity provides production-level support for the plugin, which means that you can safely use it in your systems as-is. Note that the implementation requires using a third-party library with a license that prevents us from bundling the plugin with the Curity Identity Server.

## Installing the Plugin

To install the plugin, follow these steps:

-   Download a release from the plugin's [GitHub repository](https://github.com/curityio/hardened-hashing-plugin) (also linked at the top of this page).
-   Unzip the content of the release package.
-   Copy all the JARs into `${IDSVR_HOME}/usr/share/plugins/hardened-hashing/`.

`${IDSVR_HOME}` is the installation folder of the Curity Identity Server. Inside a Docker container that uses an official image of the Curity Identity Server, the installation directory is `/opt/idsvr`. If you're not using a container, make sure to copy the JARs to every Curity Identity Server node, including the admin node, then restart the Curity Identity Server so that it can load the plugin. See also the Curity Identity Server's [product documentation](https://curity.io/docs/identity-server/developer-guide/plugins#plugin-installation) for details on installing plugins.

## Configuring the Plugin

Once you install the plugin, you can configure it in the admin UI, by following these steps:

-   Go to **Facilities** → **Password Transformers**.
-   Click on the **\+ Add** button.
-   Give the transformer a suitable name.
-   Click **Create** to create the new transformer.
-   Select one of the algorithms the plugin provides and configure its settings.

See the plugin's [README](https://github.com/curityio/hardened-hashing-plugin#configuring-the-plugin) for a detailed list of available settings for the algorithms.

Next, update a credential manager to use the newly created password transformer using these steps:

-   Go to **Facilities** → **Credential Managers** and edit a credential manager that should use the new password transformer.
-   In the **Algorithm** section select the `password-transformer` **Algorithm Type**.
-   Choose the transformer using the name you set earlier.

![A form showing the section where you add a Password Transformer to a Credential Manager](https://curity.io/images/resources/code-examples/plugins/password-transformers/add-transformer-to-credential-manager.jpg)

Commit the changes with the **Commit** option from the **Changes** menu. The Curity Identity Server will now use the new transformer when hashing passwords.

Adjust the Database Schema

Note that when you store credentials using the JDBC Plugin, the default schema defines the password column as 128 characters-wide. This might not be enough for some hashes produced by this plugin. Widen the column accordingly, by using the Liquibase changeset provided in the plugin's repository. See the [plugin's README](https://github.com/curityio/hardened-hashing-plugin#configuring-the-plugin) to check how to choose the proper column size and the [Upgrade Data Sources tutorial](https://curity.io/resources/learn/upgrade-data-sources/) to learn how to use the Liquibase tool with the Curity Identity Server.

With the password transformation plugin system you can overcome limitations and add support for both legacy and new algorithms for storing and validating passwords. This password transformer plugin enables you to use Argon2 or scrypt to protect passwords.

## More Information

Check the [Plugins Documentation](https://curity.io/docs/identity-server/developer-guide/plugins/) to learn more about installing and building plugins.
