Differences

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

--- nocode:identity-link [2019/08/13 05:58]
740803864 [Positive response]
+++ nocode:identity-link [2019/08/13 11:20] (current)
740803864 [Positive response]
@@ Line 6: / Line 6: @@
 See chapters below for details.
-===== Set up =====
+===== Setup =====
 At first, identity link must be prepared and sent to ADUCID Binder. ADUCID Binder accepts identity link HTTP requests at ''/aducid-binder/prepareIdentityLinkUpload''. Before ADUCID Binder call, **unique identifier (aka ''identityLinkId'') must be generated**. This identifier is neccessary to successfully pair identity link request and response. Let's see ADUCID Binder identity link interface parameters:
 ^ Name ^ Values ^ Mandatory ^ Description ^
@@ Line 23: / Line 23: @@
 ===== Identity link itself =====
-When identity link data are successfully uploaded, we can start identity link itself. It can be done with use of [[web-integration:client-side|Client API for Web Integration]]. We only need to specify ADUCID Binder methods to serve identity link:
+When identity link data are successfully uploaded, we can start identity link itself. It can be done with use of [[web-integration:client-side|Client API for Web Integration]]. We only need to specify right ADUCID Binder methods to serve identity link:
 <code javascript>
@@ Line 49: / Line 49: @@
 </code>
-When ''request'' value was used in identity link setup, ''data'' will be filled with service provider response. For example:
+When ''request'' value was used in identity link setup (e.g. ''{"eidProviderMethod":"READ_EID_USER_DATA","data":null}''), ''data'' will be filled in service provider response. For example:
 <code javascript>

ADUCID 4.x

User Tools

Site Tools

Differences

Page Tools