> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/service-provider-signing-certificate.md).

# Service Provider Signing Certificate

You may wish to create a resource mapping (if used) prior to carrying out this step, although this information can be added at a later date.

### Adding a Signing Certificate

1. Select ≡ > **Admin** > **Integration**.
2. In the Explorer pane, under **Single Sign On**, select **Signing Certificates**.
3. Select the **New** icon.
4. The Single Sign On Identity Provider Details window appears.Complete the details.

<table><thead><tr><th width="205">Name</th><th>Add a Display Name for the Signing Certificate</th></tr></thead><tbody><tr><td>Certificate</td><td>Choose a Certificate to make this available to your Service Provider (The Certificate dropdown field shows all certificates installed in the Local Machine store of the ASM web server)</td></tr></tbody></table>

Select the **Save** icon to save the details.

{% hint style="warning" %}
Certificates must have a private key and the IIS Application Pool must have full control of the certificate. Permissions for the certificate can be changed using **Manage Private Keys**.
{% endhint %}

### If you are using the SHA-256 Secure Hash Algorithm (a Requirement for Azure AFDS for example), ensure that :

* the certificate has been marked as exportable when it is installed
* the certificate contains the SHA-256 Signature Algorithm. You can find this information by viewing the certificate properties

{% hint style="warning" %}
An SHA256 certificate can be used to create SHA1 and SHA256 signatures. A SHA1 certificate cannot be used to create SHA256 signatures.
{% endhint %}


---

# 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://docs.alemba.com/asm/asm-hermes/integrate/managing-integration/single-sign-on-using-saml/service-provider-signing-certificate.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.