SSO for Microsoft RDS
  • 27 Nov 2023
  • 1 Minute to read
  • Dark
    Light
  • PDF

SSO for Microsoft RDS

  • Dark
    Light
  • PDF

Article Summary

Prerequisites

  • Liquit Workspace Agent or Internet Explorer
  • Remote Desktop Protocol (RDP) files that are used for SSO must be signed

To facilitate SSO authentication for a new package imported from the RDS connector we need to create a "Credential" entity in the Liquit Workspace.

Creating a credential template in Liquit Workspace

  1. Navigate to Manage > Authentication > Credential Store and click enlarge Create.
  2. In the Create credential dialog box that opens:
    • In Type, select Template and click Next
    • In Overview, insert a name and description for your template
    • In Credentials specify a variable username and a variable password for the SSO authentication. Choose whether you want to verify the provided password. Password will be verified when the user enters their credentials.
  3. Navigate to the package imported from the RDS connector and open it.
  4. Navigate to Releases > Actions

assign-credential-to-package-action

Assigning the credential

The credential template can be assigned in two ways. At the connector level and all packages that are imported will inherit the credential. Or you can overwrite the connector credential and assign it directly to a package.

At the RDS connector level
In the RDS connector > Settings screen > the Network Credentials field.

At package level
It can be assigned only to actions that support a device context.

  1. Create a package from the Liquit Setup Store manually or import apps through the synchronization method.
  2. Navigate to Releases > Actions.
  3. Edit or create a new action that supports a device context.
  4. In the Advance tab of the action:
    • In Context, select Device.
    • In Network Credentials, select the credential template you previously created.
Managed packages

Note that in the case of managed packages, existing actions cannot be edited nor deleted. To do so, you must convert the package to unmanaged by clicking on Modify package at the top of the Overview screen.

managed-by-connector-message.png


Was this article helpful?