• Java (using Java SDK platform)
• C# (using web service WSA)
• PHP (using web service WSA)

More examples are on this page

See Server side integration basics

ADUCID supports many ways how to integration with target application.

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 Javadoc SDK Client API

Java SDK Client API

Recommender Java client for server part of ADUCID integration.

Can be integrated in any Java project.

See also Javadoc SDK Client API

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 Javadoc Web Platform API

Java SDK Basic Architecture

See Adapters page

Use one of our for quick integration.Intsted of programming just configure your adapter and use benefits of ADUCID authentication. Currently we support these adapters:

• Tomcat adapter
• Spring security adapter

The simplest way how to integrate ADUCID to a mobile application is PEIG API described in ADUCID Mobile Application Integration manual

We support mobile application integration with ADUCID on Android and iOS.

• Android PEIG API
• iOS PEIG API

Integration of web applications supports three different types of communication between the client (web browser) and the server: redirect. URI and QR code.

Redirect adapter handles the communication between the client and the server adapter via standard HTTP redirect functionality. No adjustments or plug-ins for standard browsers are required. Client redirect adapter is part of Windows / OSX PEIG and expects an HTTP redirect to the ADUCID^® port (44240) that initiates authentication.

PEIG with redirect adapter cannot be used on a multiuser system (e.g. Terminal Server).

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.

If there is not redirect nor URI scheme managed by PEIG, ADUCID QR code is displayed. This code can be scanned using a mobile PEIG to process the request.

• Identity proofing
• Architecture
• Advanced integration manual