Differences

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

--- developers:start [2018/06/26 14:16]
tjotov
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Development using ADUCID technology ======
-This section is for advanced 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.
-==== To quick start, look at these basic authentication request using ADUCID: ====
-  * [[.:examples:java:client-api-basic|Java (using Java SDK platform)]]
-  * [[.:examples:c-sharp:basic|C# (using web service WSA)]]
-  * [[.:examples:php:basic|PHP ]][[.:examples:c-sharp:basic|(using web service WSA)]]
-More examples are [[.:examples:start|on this page]]
-====   ====
-===== Server side integration =====
-==== Before you start ====
-See [[.:basic-integration|Server side integration basics]]
-ADUCID supports many ways how to integration with target application.
-==== Web service ====
-[[.:integration:wsa|Web service ADUCID - “WSA”]] (all non-Java platfroms)
-WSA is meant for all platforms **except**** Java**. Just import WSA WSDL and you start developing.
-See also [[http://wiki.aducid.com/client-api|Javadoc SDK Client API]]
-==== 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]]

ADUCID 4.x

User Tools

Site Tools

Differences

Page Tools