Verify Domains

Use this example to help you verify that you own the public domains for ACME enterprise because you are federating it as an Enterprise Administrator in Omnissa Connect.

In this first step of configuring dynamic federation setup, you are going to enter the public domain and subdomain names that you want to federate. When you first access the federation setup in the ACME Management Organization, the federation setup defaults to the top-level domain from the email that you used to log in to Omnissa Connect. If ACME employees access Omnissa Connect from any other domain or subdomain, you must enter and verify all these domains for federation with Omnissa Connect.

Prerequisites

• Verify that you are logged in to the ACME Management Organization as an Enterprise Administrator.
• Verify that you can access the host admin console of ACME Laboratories.
• Verify that you have permissions to modify the DNS records of ACME Laboratories.

Procedure

If your DNS records already contain other TXT records, do not alter them. You are using two browser instances in this procedure, an instance of Omnissa Connect and an instance of your domain’s host admin console.

1. In Omnissa Connect, go to Set up Enterprise Federation and select Start in the Verify Domains step.
2. In the Domains text box that opens, enter acme.com and select Next.
   A .txt code is generated for the domain acme.com and displays in the Add TXT records section of the Verify Domains step.
3. In the self-service federation workflow, navigate to Verify domains > Add TXT records.
4. Copy the code that appears next to the acme.com domain name.
   • This long code is made up from letters, numbers, and symbols which you need when you open the domain’s host admin console.
   • If you are switching devices to finish the next step, make sure that you paste and save the code in a text file, so that you have it as you modify the DNS records for your domain.
5. Open the host admin console for ACME Laboratories.
6. In the host admin console, navigate to the DNS records page.
7. Add a new TXT type record to the DNS records and enter the value you copied.
8. Go back to the Verify Domains > Add TXT records step in the self-service federation workflow and select Next.
   The Verify Domains section of the workflow expands and prompts you to submit your domain for verification.
9. Select Verify.

What to do next

You modified the DNS records of your enterprise domain, acme.com, and submitted it for verification with Omnissa Connect. It might take up to 72 hours for the DNS text record change to take effect. You can proceed with the self-service federation workflow after the status of the domain you submitted for federation changes to Verified.

Move on to configuring the identity provider (IdP). We have examples for two IdPs, Micrsoft Entra ID and Okta.

• Micrsoft Entra ID - JIT
• Microsoft Entra ID - SCIM
• Okta - JIT
• Okta - SCIM