> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a new identity and associate it with the new application partition

> Step-by-step instructions to create an identity and assign it to a new HSM application partition.

<Note>
  For this step, you must log in with an identity that has a role with the Identity:Add permission. You can use the default Administrator role and Admin identities.
</Note>

Choose one of the following methods to create the identity and associate it with the application partition:

## Excrypt Manager

Perform the following steps to use Excrypt Manager to create an identity and associate it with the partition:

<Steps>
  <Step>
    Go to the **Identity Management** menu and select **Add**.
  </Step>

  <Step>
    Specify a name for the new identity.
  </Step>

  <Step>
    In the **Roles** drop-down menu, select the application partition that you created.
  </Step>

  <Step>
    Create a password and enter it in both the **Password** and **Confirm Password** fields.
  </Step>

  <Step>
    If the HSM is in FIPS mode, repeat the preceding steps to create a second identity for the same application partition.
  </Step>
</Steps>

## FXCLI

Run the **identity add** FXCLI command to create a new identity and associate it with the application partition that you created:

```shell title="FXCLI" wrap theme={null}
identity add --name [identity_name] --role [role_name] --password [identity_password]
```

If the HSM is in FIPS mode, run the command again to create a second identity for the same application partition.

## Set the identities in the configuration file

Set the name of each identity in the `<HSM>` section of the `fxpkcs11.cfg` file:

```none title="fxpkcs11.cfg" theme={null}
<CRYPTO-OPR>            [identity_name]           </CRYPTO-OPR>
# FIPS mode only: second identity
<CRYPTO-OPR2>           [second_identity_name]    </CRYPTO-OPR2>
```

<Note>
  In FIPS mode, the library logs in both identities. If the application supplies the password at login (`C_Login`), the library uses that password for both identities, so both identities must have the same password. If you provide the passwords through the `<CRYPTO-OPR-PASS>` and `<CRYPTO-OPR-PASS2>` fields or the `FXPKCS11_PASS` and `FXPKCS11_PASS2` environment variables, the two passwords can differ.
</Note>