Home / Integration plugins / RCDevs OpenOTP SMS OTP Integration

+

Send SMS OTP codes from RCDevs OpenOTP

When a user signs in through RCDevs OpenOTP, 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.

OTP codes never touch a third party

OpenOTP’s SMS hub normally routes codes through a cloud SMSC. The SMSEagle plugin keeps the request on your local network and sends the code from your own device over the cellular network.

Works in isolated and air-gapped networks

Cloud SMSC delivery needs outbound internet access from your OpenOTP server. SMSEagle sends messages on-premises over its own cellular connection, delivering OTP codes even in fully offline installations.

Predictable cost, no vendor dependency

Cloud SMSC delivery is billed per message, often at premium authentication rates. SMSEagle sends over a standard SIM at local carrier rates – no per-message fees, no external contract.

How it works

1

Login attempt

A user authenticates against an application protected by RCDevs OpenOTP and requests an SMS one-time password.

2

SMSC request

OpenOTP’s SMS hub calls the SMSEagle plugin (Custom1) with the user’s phone number and the generated OTP code.

3

Code delivery

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

Set up in about 10 minutes

Copy the SMSEagle script to OpenOTP and select it as the SMS gateway, and codes are sent by SMS.

SMSEagle sends RCDevs OpenOTP 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. Then, in System > Users, open that user and tick Enable user/password authentication (APIv1 only).
  3. Open Settings > Global settings > Network > SSL, turn off Forward HTTP to HTTPS and click Save changes.

RCDevs OpenOTP configuration

1. Download script custom1.php from our repository: https://bitbucket.org/proximus/smseagle-rcdevs_openotp/src
Place the plugin in your OpenOTP/smsc directory.

  • it will be used as “Custom 1”, but if you already use it for other configuration, you can rename file to “customX.php” and than edit “smshub_custom1” in line 27 to “smshub_customX” where X is number from 2 to 4.

2. All configuration related to SMS Gateway settings messages is done from the  SMS Gateway configuration.

Configure with:

  • SMS Gateway and choose Custom1
  • SMSC Username is username for SMSEagle API user you just created.
  • SMSC Password is password for above user.
  • SMSC Custom Name fill with SMSEagle
  • SMSC URL or address: https://SMSEagle_IP
    • where SMSEagle_IP is IP address of your gateway

You must also define SMS as OTP token for every user in MFA application:

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