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.
Documents in Interfaces & API
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:
TiQR API Description TiQR provides 10 methods for authentication and RSA cryptography: 1. tiqrStart Initializes a TiQR authentication or cryptographic session and returns a QRCode and a session ID. The request contains the following attributes: client: Client identifier (NAS) to be used in service logs (defaults to the client IP address). source: IP address of the end user system (optional). settings (optional): List of TiQR settings which will override the user/group/application server-side settings (ex.