The Hyland Healthcare Configuration Utility Server requires a client connection configured on the Hyland IdP server.
The Hyland Healthcare Configuration Utility Server must not use the same IdP client connection as the Hyland Healthcare Configuration Utility UI. Each application must have its own client connection configured on the Hyland IdP server.
To configure the IdP client:
-
Create a client connection on the Hyland IdP server for the Hyland Healthcare
Configuration Utility Server.
Tip:
Complete details on configuring a client connection on the Hyland IdP server are documented in the separate Identity and Access Management Services documentation.
-
Configure the following settings, as well as any standard required
settings.
All other settings can be left with the default values.
Setting
Value
Protocol Type
oidc
Redirect URLs
Enter an asterisk (*) to allow all URLs to return token or authorization codes.
Allowed Grant Types
Token Exchange
Allowed Scopes
group
hc.config.write
hc.config.read
Allow users to log in locally
Select Allow users to log in locally.
Front Channel Logout requires session ID
Select Front Channel Logout requires session ID.
Back Channel Logout requires session ID
Select Back Channel Logout requires session ID.
Access Token Lifetime
Recommended to be between 300 and 600 seconds (5–10 minutes). Acceptable lifetime values vary per deployment.
Client Secret must be present
Select Client Secret must be present.
-
Configure a client secret as described in the Hyland Identity and
Access Management Services documentation.
Later in this procedure, you will add the plain-text secret value to the configuration file for the Hyland Healthcare Configuration Utility Server.
- Save the client configuration.
-
Copy the Client ID value to the clipboard by clicking
the icon at the right of the Client ID field.
You will need this value in the next procedure.
- Recycle the application pool of the Hyland IdP server for the changes to take effect.