Create a Palo Alto Networks Prisma Access machine¶
Create a Palo Alto Networks Prisma Access machine so Certificate Manager - SaaS can discover and provision the certificates in one Prisma Access tenant through the Strata Cloud Manager configuration API. Certificate Manager - SaaS manages the certificates that GlobalProtect uses through TLS service profiles, and the certificates that Remote Network and Service Connection IPsec tunnels use through IKE gateways.
Explicit Proxy isn't supported
Certificate Manager - SaaS doesn't discover or provision Explicit Proxy certificates.
Before you begin¶
- The System Administrator, PKI Administrator, or Resource Owner role. If you have the Resource Owner role, you must own or belong to at least one team.
- An active VSatellite that can reach the Strata Cloud Manager API and the Palo Alto Networks token endpoint over HTTPS (port 443). By default, these are
api.strata.paloaltonetworks.comandauth.apps.paloaltonetworks.com. - A Strata Cloud Manager service account for the Prisma Access tenant, and its client ID and client secret.
- The tenant's Tenant Service Group ID (TSG ID).
- A role for the service account on that tenant that can read and write certificates, TLS service profiles, and IKE gateways, and can push configuration.
To create a Palo Alto Networks Prisma Access machine¶
- Sign in to Certificate Manager - SaaS.
- Click Installations > Machines.
- Click New, and then select PAN Prisma Access.
- On the Properties step, in Name, enter a name for the machine.
- For Owning Team, choose the team that owns the machine. System Administrators and PKI Administrators can choose any team. Resource Owners can choose only a team they own or belong to.
-
For VSatellite, choose a VSatellite that can reach the machine. A VSatellite that's the primary of a high availability group shows its number of active replicas, and Certificate Manager - SaaS can run the machine's operations on any healthy VSatellite in the group.
-
In Client ID, enter the client ID of the Strata Cloud Manager service account.
-
In Client Secret, enter the client secret of the service account.
Note
Certificate Manager - SaaS encrypts the credentials you enter and doesn't display them again. On the machine's Properties tab, they appear masked. To keep a stored credential when you edit the machine, leave its masked value unchanged. Keep your own secure record of the credentials in case you need them again.
-
In Tenant Service Group ID, enter the TSG ID of the Prisma Access tenant. Certificate Manager - SaaS requests every access token for this tenant only.
- (Optional) In API Base URL, replace the default,
https://api.strata.paloaltonetworks.com, if you use a different origin for the Strata Cloud Manager API. Enter it without a path. The URL must use HTTPS and apaloaltonetworks.comhost. -
(Optional) In Token Endpoint, replace the default,
https://auth.apps.paloaltonetworks.com/auth/v1/oauth2/access_token, if you use a different OAuth 2.0 token URL. Certificate Manager - SaaS exchanges the service account credentials for an access token at this URL. The URL must use HTTPS and apaloaltonetworks.comhost. -
(Optional) Disable Verify TLS Certificates only if a TLS-inspecting proxy sits between the VSatellite and Palo Alto Networks, and Certificate Manager - SaaS doesn't trust the proxy's certificate authority. It's enabled by default.
Warning
With verification disabled, the client secret and every private key that Certificate Manager - SaaS uploads can be intercepted.
-
Click Test Access. After the connection succeeds, click Continue. The Discovery step opens.
Note
A successful test confirms that Certificate Manager - SaaS can get an access token for the tenant and read its folder list. It doesn't check that the service account can write certificates or push configuration, so a missing permission shows up when you first provision a certificate.
-
(Optional) In Folder, enter a Strata Cloud Manager folder to discover only that folder, the folders below it, and their snippets, plus the certificates the folder inherits from the folders above it, such as Shared. Leave it empty to discover every folder in the tenant.
Strata Cloud Manager lists the Shared folder as Prisma Access. Certificate Manager - SaaS treats the two names as the same folder, so you can enter either one.
Tip
A folder discovery doesn't see the objects in sibling folders, so it reports a certificate that only a sibling folder uses as Not Bound. To see every binding, leave Folder empty.
-
(Optional) To skip certificates that have already expired, enable Exclude Expired Certificates.
-
(Optional) To include certificate authority certificates, such as trusted roots and intermediates, disable Exclude CA Certificates. It's enabled by default.
Discovery creates one installation for each TLS service profile or IKE gateway that uses a certificate. It reports a certificate that nothing uses once, with the Not Bound object type. IKE gateways that authenticate with a pre-shared key don't hold a certificate, so discovery skips them.
-
(Optional) To discover certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).
- Click Continue. The Provisioning step opens.
-
(Optional) To provision certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).
Scheduled provisioning pushes only certificates that are queued for deployment, such as renewed certificates, so renewals install during the window you choose.
-
Click Finish.
What's next?¶
After you create the machine, provision a certificate to it. You can also run discovery on the machine at any time to track the certificates in your Prisma Access tenant.