> For the complete documentation index, see [llms.txt](https://emca.emudhra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emca.emudhra.com/previous-release-versions/v4.0.13/user-manual/manage-profiles/key-profile/key-profile-creation/create-hsm-key-profile.md).

# Create HSM Key Profile

Please type the name of the profile in the designated profile name field.

Please select the profile type as HSM.

To upload the PKCS11 configuration file of the HSM, select "Upload" as the configuration type.

Instead of choosing "File," choose "Text Area" to paste the contents of the (.cfg) file into the "PKCS11 Configuration" field, which is shown in the figure below.

\
"Here is an example of a configuration file, as shown below:"

```
name = Luna
library = C:/LunaPCI/cryptoki.dll
attributes = compatibility
                    attributes(generate, *, *) = {
                    CKA_TOKEN = true
                    }
                    attributes(generate,CKO_PUBLIC_KEY,*) = {
                                                            CKA_ENCRYPT = true
                                                            CKA_VERIFY = true
                                                            CKA_WRAP = true
                                                            }
                                                            attributes(generate, CKO_PRIVATE_KEY,*) = {
                                                            CKA_EXTRACTABLE = false
                                                            CKA_DECRYPT = true
                                                            CKA_SIGN = true
                                                            CKA_UNWRAP = true
                                                            } slot = 1
```

<figure><img src="/files/fJ7RYiNSMHkOvAbRKcKn" alt=""><figcaption></figcaption></figure>

Note: If an officer selects the HSM key profile created by the Administrator, all the CA, Root CA, and OCSP certificates will be created in the HSM. The officer should enter the "HSM" PIN.

Please enter a valid HSM PIN.

Click on the "Test Connection" button. If you are using HSM or PKCS12 profile types, the Test Connection option will be enabled. The page displayed will be as shown in the figure above.

&#x20;    &#x20;

<figure><img src="/files/IQMACHAfH4FxBeZYbPSf" alt=""><figcaption></figcaption></figure>

Clicking the "Edit" button will redirect to the first step with filled details. The admin can edit the data and click on "Proceed".

In the second step, the admin should verify the entered data, sign, and authenticate using a valid email ID and token PIN as shown in the figure below.                                        &#x20;

<figure><img src="/files/WKRH2iVncKFcYl5vMBfP" alt=""><figcaption></figcaption></figure>

By clicking "Confirm", you will be redirected to the next page.                       &#x20;

<figure><img src="/files/Gc6hWsQGd9OD7tmm6msc" alt=""><figcaption></figcaption></figure>

Clicking "View All" redirects admins to the "Manage Key Profiles" page where all created profiles are visible.

Clicking on "+ New" will take the Admin to Step 1 of creating a new key profile.

The key profile that has been created will be updated on the "Manage key profile" page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://emca.emudhra.com/previous-release-versions/v4.0.13/user-manual/manage-profiles/key-profile/key-profile-creation/create-hsm-key-profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.