Palo Alto Captive Portal - REST API Configuration - RSA Ready Implementation Guide
Originally Published: 2023-03-29
This article describes how to integrate Palo Alto Captive Portal with RSA Cloud Access Service (CAS) using RSA MFA API (REST).
Configure CAS
Perform these steps to configure CAS for REST API.
Procedure
- Sign in to RSA Cloud Administration Console.
- Navigate to Platform > API Access Management > Authentication API Keys.
- Add a new Authentication API Key.
- Copy the API Key and URL to use when setting up the connector.
- Fetch the corresponding CA certificates from your Tenant URL; they will be used later in the Palo Alto configuration.
- Click Publish Changes and wait for the operation to be completed.
Your application is now enabled for SSO.
Configure Palo Alto Captive Portal
Perform these steps to configure Palo Alto Captive Portal.
Procedure
- Log in to Palo Alto Captive Portal Admin Console.
- Go to Device > Multi-Factor Authentication Profile and enter the following details copied from RSA.
- API Host: CAS hostname
- Client Key: The value of the key copied from the RSA Cloud Administration Console.
- Access ID: The name of the API Key fetched from the RSA Cloud Administration Console.
- To create the Authentication Rule, go to Device > User Identification > Authentication Portal and enter the following details.
- Mode: Choose Redirect.
- SSL/TLS Service Profile: Select the created Service Profile.
- Authentication Profile: Select the created Authentication Profile.
- Redirect Host: Specify the hostname or IP address of the Redirect Host that is accessible to the systems expected to use Captive Portal.
- Go to Objects > Authentication and create an Authentication Enforcement by providing the following details.
- Provide the Profile Name, select the Authentication Method as web-form, and select the Authentication Profile.
- Provide the Profile Name, select the Authentication Method as web-form, and select the Authentication Profile.
- Go to Policies > Authentication and create an Authentication Policy Rule by providing the following details.
- On the General tab, provide a name for the rule as shown in the following screenshot.
- On the Actions tab, under Log Settings, select the Log Authentication Timeouts checkbox.
- On the General tab, provide a name for the rule as shown in the following screenshot.
- Go to Network > Interface Management Profile and choose the profile.
- Select the Response Pages checkbox.
- Go to Device > Authentication, assign the MFA profile to the required authentication profile, and ensure that this profile is applied in the Authentication Portal and Authentication Enforcement settings. In the following example, we will use the SAML profile named RSA_SAML, which was previously used only for SAML authentication. We will now configure it to use REST API requests to RSA Cloud by enabling Additional Authentication Factors.
- Commit the changes to your firewall.
The configuration is complete.
Related Articles
To resolve 'Failed to read nst file' issue 66Number of Views Palo Alto Cloud Identity Engine - SAML My Page SSO Configuration - RSA Ready Implementation Guide 5Number of Views Palo Alto Cloud Identity Engine - RSA Ready Implementation Guide 7Number of Views RSA SecurID Access Free Trial Palo Alto Networks GlobalProtect Guide 63Number of Views Palo Alto NGFW 10.1.7 - RADIUS Configuration - RSA Ready Implementation Guide 197Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?