Before you can configure the integration between Omnissa Access and Workspace ONE UEM, to establish a connection between Omnissa Access and Workspace ONE UEM, an OAuth 2.0 service client must be configured in Omnissa Access.
The client ID and shared secret are configured in the Workspace ONE UEM console Getting Started wizard to establish the connection with Omnissa Access. See Using the Getting Started Wizard to Connect Workspace ONE UEM with Omnissa Access article in the Guide to Deploying Workspace ONE UEM with Omnissa Access.
For newly created SaaS tenants, the OAuth 2.0 service client is generated on behalf of a new Omnissa Access client when the tenant is established and is not managed from the Omnissa Access console.
For integration with an on-premises Omnissa Access deployment, the Omnissa Access admin generates the OAuth 2.0 service client in the Omnissa Access console, Settings > OAuth 2.0 Management > UEM page. The UEM admin adds the client ID and shared secret to the Getting Started wizard before integrating with Omnissa Access.
Procedure
-
In the Omnissa Access console Settings > OAuth 2.0 Management page, click UEM.
-
In the UEM page, click GENERATE CLIENT.
Enter the following client information.
Label Description Client ID Enter a unique client identifier for the application. The client ID is used to authenticate to Omnissa Access. The client ID must not match any client ID in your tenant. The following characters can be used, alphanumeric (A-Z, a-z, 0-9) period (.), underscore (_), hyphen (-) and at sign (@).The client identifier can be no more than 256 characters. UEM Server URL Enter the URL of your Workspace ONE UEM server that will be integrated with the Omnissa Access server. -
Click GENERATE CLIENT.
The UEM client is created and a shared secret is generated. The client page is refreshed to display the UEM Service Client settings.
Field Value and Description Access type Service Client Token Client ID The name you created for the UEM Client ID is displayed Scope The scope is Admin. The Admin scope allows access to the admin APIs. Issue refresh token Activated. This allows for the return of a refresh token. Access token TTL 7 days. This is the time after which the access token is expired. When the access token expires, the refresh token is used to request a new access token. Refresh token TTL 1 month. This is the time to live value of the refresh token. New access tokens can be requested until the refresh token expires. Idle token TTL 0 -
Before leaving this page, copy and save the client ID and generated shared secret. You add this information before you configure Omnissa Access service in the Workspace ONE UEM console to establish the connection between Workspace ONE UEM and Omnissa Access services.
Note: The shared secret is not saved. If you loose the secret code, you must generate a new secret, and update the app that uses the same shared secret with the regenerated secret.
To regenerate a secret, click the client ID that requires a new secret from the OAuth 2.0 Management page and click REGENERATE SECRET.
You cannot delete the OAuth 2.0 UEM Client that you create.
What to do next
Log in to your Workspace ONE UEM console and add the Client ID and shared secret to the Groups & Settings > All Settings > System > Enterprise Integration > Omnissa Access > Configuration page. See the Guide to Deploying Workspace ONE UEM with Omnissa Access.
Was this page helpful?