
Parameter Storage in SailPoint ISC
Date Posted:
7 Nov 2025
Category:
Security

Parameter Storage in SailPoint ISC
Date Posted:
7 Nov 2025
Category:
Security

Parameter Storage in SailPoint ISC
Date Posted:
7 Nov 2025
Category:
Security
Understanding Parameter Storage in SailPoint Identity Security Cloud
Introduction Of Parameter storage in SailPoint ISC
Parameter Storage is a feature in SailPoint ISC that allows you to store credentials and other configuration parameters directly within the platform. This eliminates the need for external vaults or hardcoded credentials.
In Privileged Task Actions (PTA), Parameter Storage functions as an integrated credential provider. Instead of depending on external credential sources, you can store authentication details once within ISC and reuse them across multiple workflow actions.
How to use it
Go to Admin → Global → Parameter Storage.

Decide which credential you want to store centrally (for example: service account username/password, API client secret, domain controller bind account etc).
If the category is Authentication: types like Credential, Azure Entra ID Client, HTTP Custom Auth, OAuth 2 Client Credentials etc.
If the category is Connection: types like Active Directory, Entra ID, Server Address, WebApp, Kerberos etc.


After storing the parameter (with the secret / credentials) you can reference it from workflows or privileged task actions. For example, when configuring a workflow action for AD or Windows Server, you can choose Connection = Parameter Storage and Authentication = Parameter Storage and select the parameter you created.
In your workflow where you previously might have entered credentials inline, choose Parameter Storage for the Authentication field and select the parameter you created.
If you also have connection config (hostnames, ports, domains) that you reuse across actions, consider storing those in Parameter Storage under category Connection.

Edit the parameter to update the configurations except type and category. Parameters that are in use cannot be deleted.

Conclusion
By using the parameter storage, credentials can be securely referenced in workflows and other configurations, ensuring better security and easier maintenance.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Category:
Security
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Stay tuned to our blog to see more posts about
Sailpoint products implementation and its related updates.
Category:
Category:
Security
Security
Get your
Tailored Quote for your
Organisation
Get your
Tailored Quote for your
Organisation
Understanding Parameter Storage in SailPoint Identity Security Cloud
Introduction Of Parameter storage in SailPoint ISC
Parameter Storage is a feature in SailPoint ISC that allows you to store credentials and other configuration parameters directly within the platform. This eliminates the need for external vaults or hardcoded credentials.
In Privileged Task Actions (PTA), Parameter Storage functions as an integrated credential provider. Instead of depending on external credential sources, you can store authentication details once within ISC and reuse them across multiple workflow actions.
How to use it
Go to Admin → Global → Parameter Storage.

Decide which credential you want to store centrally (for example: service account username/password, API client secret, domain controller bind account etc).
If the category is Authentication: types like Credential, Azure Entra ID Client, HTTP Custom Auth, OAuth 2 Client Credentials etc.
If the category is Connection: types like Active Directory, Entra ID, Server Address, WebApp, Kerberos etc.


After storing the parameter (with the secret / credentials) you can reference it from workflows or privileged task actions. For example, when configuring a workflow action for AD or Windows Server, you can choose Connection = Parameter Storage and Authentication = Parameter Storage and select the parameter you created.
In your workflow where you previously might have entered credentials inline, choose Parameter Storage for the Authentication field and select the parameter you created.
If you also have connection config (hostnames, ports, domains) that you reuse across actions, consider storing those in Parameter Storage under category Connection.

Edit the parameter to update the configurations except type and category. Parameters that are in use cannot be deleted.

Conclusion
By using the parameter storage, credentials can be securely referenced in workflows and other configurations, ensuring better security and easier maintenance.
