Explicit Proxy Mobile Users

From the Panorama that manages Prisma Access, set up and configure a Mobile Users—Explicit Proxy deployment.

Before you configure Explicit Proxy guidelines, be aware of how explicit proxy works and how explicit proxy identifies users, go through the planning checklist, and learn how to set up the Explicit Proxy PAC file.

From the Panorama that manages Prisma Access, install the Panorama device certificate.

You must generate a one-time password (OTP) and retrieve the device certificate to successfully authenticate Panorama with the Cloud Identity Engine.

Log into the Customer Support Portal to generate the One Time Password (OTP).

Select

Assets

Device Certificates

and

Generate OTP

.

For the

Device Type

, select

Generate OTP for Panorama

and

Generate OTP

.

Select the

Panorama Device

serial number.

Generate OTP

and

Copy to Clipboard

.

From the Panorama that manages Prisma Access, select

Panorama

Setup

Management

Device Certificate Settings

and

Get certificate

.



When you have successfully installed the certificate, the

Current Device Certificate Status

(

Panorama

Setup

Management

Device Certificate

) displays as

Valid

.



From the hub, activate the Cloud Identity Engine if you have not yet done so to create your first instance.

Log in to the hub.

You can view apps by tenant or by support account.

Activate

the Cloud Identity Engine.

If the Activate button is not available, ensure that your role has the necessary privileges.



Enter the information for your Cloud Identity Engine instance.



Select the
Company Account
for the instance.
Specify an
Name
to identify the instance.
(
Optional
) Enter a
Description
to provide more information about the Cloud Identity Engine instance (for example, details about the instance’s purpose).
Select a
Region
.
Make a note of the region; you specify the same region when you create an authentication profile in Panorama.
Agree to the
EULA
.

Agree & Activate

the instance.

On the Activation Details page, select the hub in the upper left.



The

Cloud Identity Engine

displays.



(

Optional

) If you require a separate instance for Explicit Proxy, configure a Cloud Identity Engine Instance.

If you want to isolate your Explicit Proxy directory data, or allow different Palo Alto Networks cloud applications and services to access different sets of directory data, you can create a Cloud Identity Engine instance specifically for Explicit Proxy.

Log in to the hub.

Click the gear in the upper right corner of the page to manage the settings; then, select
Manage Apps
and click
Add Instance
.

Configure the instance.

Select the
Company Account
for the instance.
Specify an
Name
to identify the instance.
(
Optional
) Enter a
Description
to provide more information about the Cloud Identity Engine instance (for example, details about the instance’s purpose).
Select a
Region
.
Make a note of the region; you specify the same region when you create an authentication profile in Panorama.
Agree to the
EULA
.
Agree & Activate
the instance.

From the Cloud Identity Engine app, configure a SAML 2.0 IdP in the Cloud Identity Engine.

The Cloud Identity Engine Getting Started guide has the procedures you need to configure a SAML IdP in the Cloud Identity Engine:

Configure Azure as an IdP in the Cloud Identity Engine
Configure Okta as an IdP in the Cloud Identity Engine
Configure PingOne as an IdP in the Cloud Identity Engine
Configure PingFederate as an IdP in the Cloud Identity Engine
Configure Google as an IdP in the Cloud Identity Engine

Do not configure single logout, it is not supported. .

Set up an authentication profile in the Cloud Identity Engine and select the users and groups that can use this authentication method.

You specify this profile when you create an authentication profile in Panorama in a later step.

Return to the Panorama that manages Prisma Access and configure an authentication profile to use with the Cloud Authentication Engine.

Select

Device

Authentication Profile

and

Add

an authentication profile.

Be sure that you are in the

Explicit_Proxy_Template

.

Enter a

Name

for the Authentication profile.

Select

Cloud Authentication Service

as the

Type

.

Select the

Region

of your Cloud Identity Engine instance.

Specify the same region you used when you created your Cloud Authentication Engine instance.

Select the Cloud Identity Engine

Instance

to use for this Authentication profile.

Select an authentication

Profile

that specifies the authentication type you want to use to authenticate users.

Specify the authentication profile you created in the Cloud Identity Engine.

Specify the

Maximum Clock Skew (seconds)

, which is the allowed difference in seconds between the system times of the IdP and the firewall at the moment when the firewall validates IdP messages (default is 60; range is 1–900). If the difference exceeds this value, authentication fails.

(

Optional

) If the profile you selected has multi-factor authentication (MFA) enabled, select

Force multi-factor authentication in cloud

.

Selecting this option means that the IdP (for example, Okta) specified by the profile is responsible for performing MFA. If you select this check box and incorrect MFA information is received from the Cloud Identity Engine, authentication fails.

Click

OK

.



Allow the necessary authentication traffic to be passed to Explicit Proxy.

Create a URL list as a custom URL category to allow the necessary traffic for the Cloud Identity Engine.
Add the following Cloud Identity Engine URLs to the URL category.
If you do not need to strictly limit traffic to your region, you can enter
*.apps.paloaltonetworks.com
. Otherwise, determine your region-based URL using the
show cloud-auth-service-regions
command in the Cloud Identity Engine to display the URLs for the region associated with your Cloud Identity Engine instance and enter each region-based URL. The following table includes the URLs for each region:
Region	Cloud Identity Engine Region-Based URL
United States	cloud-auth.us.apps.paloaltonetworks.com cloud-auth-service.us.apps.paloaltonetworks.com
Europe	cloud-auth.nl.apps.paloaltonetworks.com cloud-auth-service.nl.apps.paloaltonetworks.com
United Kingdom	cloud-auth.uk.apps.paloaltonetworks.com cloud-auth-service.uk.apps.paloaltonetworks.com
Singapore	cloud-auth.sg.apps.paloaltonetworks.com cloud-auth-service.sg.apps.paloaltonetworks.com
Canada	cloud-auth.ca.apps.paloaltonetworks.com cloud-auth-service.ca.apps.paloaltonetworks.com
Japan	cloud-auth.jp.apps.paloaltonetworks.com cloud-auth-service.jp.apps.paloaltonetworks.com
Australia	cloud-auth.au.apps.paloaltonetworks.com cloud-auth-service.au.apps.paloaltonetworks.com
Germany	cloud-auth.de.apps.paloaltonetworks.com cloud-auth-service.de.apps.paloaltonetworks.com
United States - Government	cloud-auth-service.gov.apps.paloaltonetworks.com cloud-auth.gov.apps.paloaltonetworks.com
India	cloud-auth-service.in.apps.paloaltonetworks.com cloud-auth.in.apps.paloaltonetworks.com
Enter the URLs that your IdP requires for user authentication (for example,
*.okta.com
) in the custom URL category.
Create a security policy rule to allow traffic to the authentication type and Cloud Identity Engine and select the custom URL category as the match criteria.

Specify the authentication profile for Explicit Proxy.

Select

Panorama

Cloud Services

Configuration

Mobile Users—Explicit Proxy

.

Select the

Connection Name

.

Specify the Cloud Identity Engine

Authentication Profile

.



Commit and Push

your changes.

Verify that the Cloud Identity Engine is successfully authenticating your Explicit Proxy mobile users.

From the Panorama that manages Prisma Access, select

Monitor

Logs

Authentication

.

View the

Event

status.



If the authentication fails, view the

Description

for more details about the failure.



From the mobile user’s endpoint, use dev tools to view the Cloud Identity Engine authentication flow.