Generating a Secret for the Service Account Client - Generating a Secret for the Service Account Client - Perceptive Content - OnBase - Other - Identity and Access Management Services - Other/Identity-and-Access-Management-Services/5.3/Identity-and-Access-Management-Services/Configuring-Providers-and-Clients-Using-the-IdS-Service-Account/Generating-a-Secret-for-the-Service-Account-Client - 5.3 - 5.3

Identity and Access Management Services

Platform
Other
Product
Identity and Access Management Services
Release
5.3
License
ft:lastPublication
2026-05-22T12:39:50.585000
ft:locale
en-US

A secret for the Service Account Client can be generated in the following scenarios:

  • During the initialization process for new installations. For more information on the initialization process, see Initializing Hyland IdS.
  • When a user generates a client secret using the graphical user interface or the command line utility.
Note: The secret for the Service Account Client is displayed only once and is kept as a hashed value in the system.

To provide an extra layer of security, Hyland Identity Service (IdS) encrypts client secrets and API secrets using the Hyland Application Settings Utiltity (HASU). For detailed instructions, see Encrypting Client Secrets and API Secrets.

The following limitations apply when generating a secret for the Service Account Client:

  • The maximum secrets that a user can generate is set to 2. If there are 2 secrets and a new secret is required to be generated, either of the secrets must be deleted.
  • The expiration date of the secret is restricted to a maximum of 180 days from the date of creation. A user can enter a custom expiry date, which should not be more than 180 days.

The Service Account Client must be enabled if you want to manage its secrets. For information on enabling the Service Account Client, see the topics under Managing Service Account Client.

For more information on creating or deleting secrets from the Service Account Client using the command line utility or the graphical interface, see the topics under: