---
title: "exSsoSamlPrereqs"
canonical: "https://help.agiloft.com/space/HELP/65341125/exSsoSamlPrereqs"
format: markdown
---
> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - A public certificate and private key pair stored in the Java KeyStore (JKS) on the Agiloft CLM server are used to sign, encrypt, and decrypt the SAML XML that is exchanged between Agiloft CLM and your IdP. As part of the setup, you supply the JKS file path, password, and alias for your Agiloft CLM server. If your KB is hosted by Agiloft, [contact Support](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43716690) to get this information. If your KB is self-hosted, you may need to [generate a key pair](#generate_keystore).
> ℹ️ - By default, Agiloft CLM supports the standard SHA-256 and SHA-512 cipher transformations for encrypting SAML messages. While these transformations suffice for most commonly used IdPs, you can configure your KB to use an alternate transform by setting the Custom Cipher transform for decrypting SAML Keys [global variable](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43713942).
> ℹ️ - Agiloft CLM supports just-in-time user provisioning with SAML, which creates or updates user records when users log in with SSO. If you need broader user lifecycle management, such as automatically provisioning and updating users based on changes in your IdP, you can use SCIM provisioning instead. See [Provision Users with SCIM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779649034) for more information.