User Tools

Site Tools


developers:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
developers:start [2018/06/27 14:37]
tjotov [Before you start]
— (current)
Line 1: Line 1:
-====== Server side development ====== 
-This section is for advanced forms of integration when [[integration:start|No-code integration]] cannot be used or isn't sufficient. This includes advanced scenarios like M2M, Wi-Fi or VPN integration. 
- 
-==== Before you start ==== 
-Learn about integration basic integration concepts 
-  * [[developers:basic-overview|Server side integration basics]] 
- 
-Learn about ADUCID  Integration API to connect server side application and server back-end  
-  * [[integration-api:start|ADUCID Integration API]] 
- 
-Learn about mobile application integration 
-  * [[developers:peig-api|Developing a mobile application with ADUCID]] 
- 
- 
-===== Supported scenarios ===== 
-==== Web service ==== 
- 
-[[.:integration:wsa|Web service ADUCID - “WSA”]] 
- 
-WSA is a web service integration. To start development just import WSDL. 
- 
- 
-==== Java SDK platform ==== 
- 
-[[.:integration:sdk-java:client-api|Java SDK Client API]] 
- 
-Recommender **Java**  client for server part of ADUCID integration. 
- 
-Can be integrated in any Java project. 
- 
-See also [[http://wiki.aducid.com/client-api|Javadoc SDK Client API]] 
- 
-[[.:integration:sdk-java:web-platfrorm|Java SDK Web Platform]] (Tomcat only) 
- 
-The simplest way is to integrate a **Java web application**  with ADUCID. It is based on Java SDK Client API. It implements all necessary calls directly to your application returning authentication (operation) result into your session variables. 
- 
-Ideal when you are starting a new web Java project. 
- 
-See also [[http://wiki.aducid.com/web-platform|Javadoc Web Platform API]] 
- 
-[[.:integration:sdk-java|Java SDK Basic Architecture]] 
- 
- 
-===== Integration with mobile applications ===== 
- 
-The simplest way how to integrate ADUCID to a mobile application is PEIG API described in [[.:peig-api|ADUCID Mobile Application Integration manual]] 
- 
-We support mobile application integration with ADUCID on Android and iOS. 
- 
-  * [[.:peig-api:android|Android PEIG API]] 
-  * [[.:peig-api:ios|iOS PEIG API]] 
- 
-===== Integration with web browsers ===== 
-TODO BETTER 
- 
-Integration of web applications supports two types of communication between the client (web browser) and the server: URI and QR code. 
- 
-==== URI scheme ==== 
-The current operating system (including mobile phone operating systems and workstation operating systems) brings a new way of secure communication between applications in a protected user space. It is the registered, specific URI schema. 
- 
-If the supporting application is registered in the operation system with the URI schema during installation, the operating system ensures activation of the registered application and transfer of the URI parameters to the application. 
- 
-This option is used by PEIG for mobile phones. 
- 
-==== QR code ==== 
-QR code is displayed by aducid-binder. This code can be scanned using a mobile PEIG to process the request. 
- 
-===== Further reading ===== 
- 
-  * [[:documentation:identity-proofing|Identity proofing]] 
-  * [[:documentation:architecture|Architecture]] 
-  * [[.:advanced-integration:start|Advanced integration manual]] 
- 
  
developers/start.1530110253.txt.gz · Last modified: 2018/06/27 14:37 by tjotov