Home / Integration plugins / Check Point SMS Integration

+

Send SMS OTP codes from Check Point

When a user signs in through Check Point Mobile Access with DynamicID, the one-time code is sent by SMS through SMSEagle, your own hardware SMS gateway. The request stays in your local network, with no cloud SMS provider.

Direct API call, no middleman SMS provider

Check Point’s DynamicID SMS Provider setting talks straight to SMSEagle’s HTTP API over your network, so authentication codes don’t need to pass through an external cloud SMS service you don’t control.

Keeps working when the internet doesn't

SMSEagle sends over its own SIM card, on-premises and independent of your internet connection, so DynamicID codes are still sent during an outage that would take a cloud SMS provider down with it.

Predictable cost, no per-message billing

SMSEagle sends over a standard SIM at local carrier rates, so as login volume grows, your cost doesn’t scale with every message.

How it works

1

Sign-in

A DynamicID login attempt or a Mobile Access authentication request triggers Check Point’s gateway to send a one-time code.

2

API call

The configured SMS Provider URL sends a request straight to SMSEagle’s API, with the recipient number and message filled in.

3

Code delivered by SMS

SMSEagle delivers the code over its own cellular connection, not through a third-party service, as an SMS to the user’s phone.

Set up in about 10 minutes

No SMS provider subscription required. With a single SMS Provider URL pointed at SMSEagle’s HTTP API, Check Point’s DynamicID starts sending one-time codes by SMS in minutes, using your own hardware and your own SIM.

SMSEagle sends Check Point one-time codes by SMS from your own device, with no cloud SMS provider.

Works on any phone

An SMS code needs no app: people receive it on any mobile phone.

Every code sent is recorded

SMSEagle records every code it sends, together with its status, so you can check whether it was received.

Logins work even if one device fails

Two SMSEagle devices can work as an HA cluster: if one fails, the other takes over sending codes.

SMSEagle configuration

  1. Create a new user in SMSEagle (menu System > Users) with access level “User”.
  2. Grant API access to the created user:
    • go to Settings > Global settings > API and open the API v1 page
    • click Create API key, fill in Key name and select that user as Owner
    • Add access permissions in section Permissions for: Send SMS, Send to contact, Send to group
    • click Create key. The access token is shown only once, right after saving.

 

Check Point configuration

Checkpoint Setup

  1. In order to configure SMSEagle with Checkpoint DynamicID, please go to GW configuration -> Mobile Access -> Authentication
  2. Under DynamicID Settings click on „Edit”
  3. In newly opened window „SMS Provider and Email Settings” paste SMSEagle API URL:
    https://SMSEagle_IP/http_api/send_sms?access_token=XYZAPI&to=$PHONE&message=$MESSAGE
    where SMSEagle_IP is SMSEagle’s IP address, and XYZAPI is access_token created for your user in SMSEagle webUI
  4. Important information:
    Remember to use a SSL certificate issued by a recognizable CA. LetsEncrypt is treated as unsafe CA on CheckPoint.

Explore SMSEagle Demo device

SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.

After registering to a demo you get a remote access to our physical device NXS-9750.

  • 14-days free trial
  • Access to over 20 functionalities

What is hardware
SMS Gateway?

Learn more about
SMSEagle features