Configure Check Point to interoperate with Okta via RADIUS

This guide details how to configure Check Point to use the Okta RADIUS Server AgentA software agent is a lightweight program that runs as a service outside of Okta. It is typically installed behind a firewall and allows Okta to tunnel communication between an on-premises service and Okta's cloud service. Okta employs several agent types: Active Directory, LDAP, RADIUS, RSA, Active Directory Password Sync, and IWA. For example, users can install multiple Active Directory agents to ensure that the integration is robust and highly available across geographic locations. in conjunction with the Okta Integration Network (OINAn acronym for the Okta Integration Network. The OIN is comprised of thousands of public, pre-integrated business and consumer applications. As an on-demand service, OIN integrations are continuously validated, always up to date, and constantly growing both in number and capability. Okta performs a single integration with an ISV or SP, providing thousands of end users with point-and-click customization for their orgs.) Check Point Software (RADIUS) appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in..

Check Point integrates with multiple third party identity stores via RADIUS, TACAS+, LDAP, Kerberos, AD Query, and Cisco pxGrid. Okta and Check Point interoperate through RADIUS. Using RADIUS, Okta’s agent translates RADIUS authentication requests from Check Point into Okta API calls.

There are five parts to the configuration. Troubleshooting help and a list of additional resources are also provided.

Top