Step 1. Create a Microsoft Entra ID application

1. Log in to the Microsoft Azure portal https://portal.azure.com/#home.

2. Open the portal menu and select Microsoft Entra ID.

3. On the left pane, select App registrations.

1. Click New registration (at the top of the right pane). The Register an application blade opens.

1. In the Name field, type the name you want to use for the application.

2. Select an appropriate account type.

3. In the Redirect URI section, make sure that Web is selected in the drop-down list and add the following URIs:

   https://pbi.parallels.com/rbi/oidc/signin/callback and https://pbi.parallels.com/owner/test-idp.

1. Click Register (at the bottom left).

Step 2. Create a client secret for the Microsoft Entra ID application

1. If you are not on the application page anymore, navigate to it from the Home page by selecting Microsoft Entra ID > App registration and then clicking the app in the right pane.

2. In the left pane, click Certificates & secrets.

3. In the right pane, click New client secret.

4. Type a client name and select a desired expiration option.

5. Click Add. The new client secret appears in the Client secrets list.

Step 3. Configure a token

1. Select your application and on the left pane, select Token configuration.

2. Click Add groups claim.

1. Select an appropriate group type.

2. Click Add.

3. Click Add optional claim.

4. In the Token type section, select ID.

5. Select preferred_username.

1. Click Add.

Step 4. Assign Required Permissions to the Microsoft Entra ID application

1. Select your application and on the left pane, select API permissions.

2. Click Add a permission.

3. Click the Microsoft Graph card.

4. Click the Delegated permissions card.

5. Open the Group section.

6. Select the following permissions:

   • Group.Read.All

1. Click Add permissions.

2. Click Grant admin consent for...

3. Confirm you want to grant admin consent by clicking Yes.

Step 5. Save settings for future use

1. Select your application and on the left pane, select Overview.

2. Save the following information for use in the Parallels Browser Isolation Management Portal setup:

   • Application (client) ID

3. Click the Endpoints button.

4. Save the value of the OpenID Connect metadata document field for use in the Parallels Browser Isolation Management Portal setup.

Make sure to securely store the client secret and other sensitive information.

Step 6. IdP Configuration on PBI Owner Portal

1. Once the above steps are completed, copy the values from Entra ID which should mimic the table below, and paste them into the Parallels Browser Isolation IDP configuration section as shown below:

1. Click Save and proceed with adding users using the Admin Management section that was configured in the OIDC.

1. Log in to the Google Cloud Console at .

2. At the top of the page, click Select a Project or New Project.

1. In the left menu (or under Quick access on the page), click on APIs & Services, then OAuth consent screen.

2. In the User Type section, select Internal.

1. Fill in Application name and Support email fields, and click Save and Continue.

1. Add email, profile, and openid.

1. Click the Create credentials button, and select OAuth client ID.

1. Fill in the details below and click Create. Application Type: Web application Name: [Name of you application] Authorized redirect URIs: https://pbi.parallels.com/rbi/oidc/signin/callback and https://pbi.parallels.com/owner/test-idp. This is the Parallels Browser Isolation redirect URL.

1. In the dialog that appears, copy the Client ID and Client Secret or download the JSON file.

2. Once the above steps are completed, copy the values which should mimic the table below, and paste them into the Parallels Browser Isolation IDP configuration section as shown below:

1. Click Save and proceed with adding users using the Admin Management section that was configured in the OIDC.

Step 1. Create an application

1. Log in to https://manage.auth0.com/.

2. Navigate to Getting started and click Create Application.

3. Do one of the following:

   • If you don't have any specific requirements for your environment, select either Single Web Page Applications or Regular Web Applications.

   • If you know that your environment requires a specific type of application, select that type.

4. Click Create.

5. Select the Settings tab and copy the values of Client ID and Client Secret.

6. In the Allowed Callback URLs field, specify https://pbi.parallels.com/rbi/oidc/signin/callback and https://pbi.parallels.com/owner/test-idp.

7. Select the Endpoints tab in the Advanced settings section and copy the value of the OpenID Configuration field.

Step 2. Adding users

1. In the left pane, navigate to Users under User Management.

2. Navigate to Create Users and click Create User.

3. Add the email and password of the user.

4. (Optional) Verify the user's email:

   1. Click the three dots button.

   2. In Details, go to email and verify the email.

Step 3. IdP Configuration

1. Once the above steps are completed, copy the values from which should mimic the table below, and paste them into the Parallels Browser Isolation IDP configuration section as shown below:

1. Click Save and proceed with adding users using the Admin Management section that was configured in the OIDC.

1. On your Okta admin dashboard, go to Applications > Applications.

2. Select Create App Integration.

3. In the Sign-in method section, select OIDC - OpenID Connect.

1. In the Application type section, select Web Application. Click Next.

2. Enter a name for the application as relevant to your organization. For example, Acme Inc.

3. In the Sign-in redirect URIs field, specify https://pbi.parallels.com/rbi/oidc/signin/callback and https://pbi.parallels.com/owner/test-idp.

4. On the General tab, copy the Client ID and Client secret.

1. Once the above steps are completed, copy the values from OKTA which should mimic the table below, and paste them into the Parallels Browser Isolation IDP configuration section as shown below:

1. Click Save and proceed with adding users using the Admin Management section that was configured in the OIDC.