Omnissa Identity Services with Directory Services

If you use Omnissa products Omnissa Workspace ONE UEM, Omnissa Access, and Horizon, and find yourself having to manage the same set of users in each product, you can integrate Identity Services with your directory services. Identity Services lets you implement Federated identity for user accounts and authentication, provide support for service accounts and customer applications, and utilize common tenancy models and authorization patterns across these Omnissa products.

For more information, see the Identity Services Guide.

Technical Preview: Support for Certain Workspace ONE UEM Username and Password-based Flows (Password Grant Flows)

Some Workspace ONE UEM flows that rely on username and password-based authentication are supported only if you select OpenID Connect as the authentication protocol in Omnissa Identity Services and enable the Password Grant setting on the Workspace ONE UEM Directory Services page to grant permission to use the legacy Password grant protocol. These flows include:

For information about configuring the Password Grant setting, see the Enable the Password Grant setting section.

Enable the Password Grant setting

If you use certain Workspace ONE UEM username and password-based flows, you must enable the Password Grant setting on the Workspace ONE UEM Directory Services page to grant permission to use the legacy Password grant protocol. You must also select OpenID Connect as the authentication protocol in Omnissa Identity Services.

These requirements apply to the username and password-based flows listed in Support for Certain Workspace ONE UEM Username and Password-based Flows.

To enable the Password Grant setting:

1. In the Workspace ONE UEM console, navigate to the Accounts > Administrators > Administrator Settings > Directory Services page.

2. Enable the Password Grant setting.

   

Important: Although the Password grant protocol is not recommended by the OAuth 2.0 Security Best Practices document, Omnissa Identity Services is using it to support certain legacy authentication flows that rely on password-based authentication only. Its use is strictly limited to those flows.