Documents in Interfaces & API

API examples

1. Manager API The Manager interface provides access to some WebADM user management functions and operations exported by your registered applications. The Manager also allows external systems such as Web portals to remotely trigger user management operations and actions from the network. The user management functions provide LDAP operations such as object creation, update, removal, WebADM settings and data management, etc… The method names for internal management functions are in the form Manager_Method.


OpenOTP API Description The OpenOTP authentication service is implemented over the SOAP/XML and RADIUS APIs. The SOAP/XML API is provided with a SOAP WSDL service description listed below. The OpenOTP API is very simple and provides 4 methods: 1. openotpNormalLogin and openotpSimpleLogin These methods are used to send an authentication request. The request contains the following attributes: username: User login name (mandatory). domain: User login domain (optional if OpenOTP as a default domain setting set).


OpenSSO SOAP API Description Usage OpenSSO provides a very simple API to enable OpenOTP single sign-on across several web application. The API allows setting, removing and checking SSO sessions. The SSO session IDs should be given to the end users in Web browsers’ cookies. A typical usage of OpenSSO is: **User authenticates on Server1:** The web application on Server1 performs the following SOAP calls to the WebADM server. - failure : Do not start a SSO session - success : Start a SSO session 3.


SMSHub API Description OpenOTP SMSOTP is only possible via Clickatell online SMS SOAP service and via RCDevs SMSHub which is a WebADM service application just like OpenOTP. SMSHub proposes much more options than the OpenOTP basic SMS functionalities but if you use the Clickatell service only, then you do not need it. SMSHub does not send SMS directly and will use Clickatell or another online SMS service. But with SMSHub you can:

EAP and Certificate based authentications

1. Overview This guide explains how to deploy certificate-based authentications for users and computers using 802.1x with RCDevs solutions. This solution can be applied to Wireless LAN / Wired LAN networks, RCDevs Web applications and also custom integrations like certificate-based authentication on your own website through OpenOTP APIs. It also describes how to implement EAP-TTLS authentication and certificate based authentication through OpenOTP APIs. All integrations require at least WebADM product installed and running.

OpenOTP Electronic Signature and Secure Transaction Approval

1. Overview and Requirements RCDevs offer now an easy way to sign any documents at anytime to all third party signatories. OpenOTP signature is a solution which is deployed on premise or in the cloud. Integrate OpenOTP signature in your infrastructure will allow electronic signatures for your company users (LDAP users). If you want to extend your signature processes to external users (users not part of your LDAP directory/directories configured with your WebADM), you have to integrate OpenOTP with YumiSign platform which requires a YumiSign API Key configured in OpenOTP settings.