Configuring the IdP Client for the Hyland Preferences Service - Hyland Clinician Window - 23.3 - 23.3 - Other - external

Hyland Clinician Window

Platform
Other
Product
Hyland Clinician Window
Release
23.3
License

The Clinician Window API requires a client connection to be configured specifically for the Hyland Preferences Service on the Hyland IdP server.

To configure an IdP client for the Hyland Preferences Service:

  1. Create a client connection on the Hyland IdP server for the Hyland Preferences Service.
    Tip:

    Complete details on configuring a client connection on the Hyland IdP server are documented in the separate Identity and Access Management Services documentation.

    The client connection must have 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

    Allowed Grant Types

    Select Authorization Code, Password, Device Code, and Token Exchange.

    Allowed Scopes

    openid, group, psw.preferences-service, offline_access

    Allow users to log in locally

    Select Allow users to log in locally.

    Allow clients to request a refresh token

    Select Allow clients to request a refresh token.

    Allow issuing access tokens to browsers

    Select Allow issuing access tokens to browsers.

    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.

    Include user claims in ID token

    Select Include user claims in ID token.

    Client Secret must be present

    Select Client Secret must be present.

  2. After saving the client connection, copy the Client ID value to the clipboard by clicking the icon at the right of the Client ID field.
  3. Create a client secret on the Hyland IdP server for the Hyland Preferences Service client connection.
    Tip: Complete details on configuring a client secret on the Hyland IdP server are documented in the separate Identity and Access Management Services documentation.
  4. Recycle the application pool of the Hyland IdP server for the changes to take effect.