This is an old revision of the document!
You can follow these steps to integrate no-code identity link support to your application:
See chapters below for details.
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 |
---|---|---|---|
identityLinkId | String | Yes | identity link unique identifier |
remoteAims | List<String> | Yes | list of identity link remote AIMs |
peigMessage | MultipartFile | No | identity link message in plain or HTML format |
peigMessageData | MultipartFile | No | identity link message data |
initLF | Boolean | No | if true, personal code will be initialized |
redirectUrl | String | Yes | URL to redirect after ADUCID Binder successful authentication |
errorPage | String | No | URL to redirect after ADUCID Binder unsuccessful authentication |
udi | String | No | if defined, security attack check is realized |
request | String | No | if defined, syncMyIdentityLinkedUserData method is called with this provided |
It is neccessary to add transactionId
parameter to redirectUrl
attribute to successfully pair transaction request and response. If errorPage
is not defined, redirectUrl
is used in case of error. Now we can send prepared request to /aducid-binder/prepareTransactionUpload
and check successful transaction upload (HTTP code 200).
We must also remember to provide generated transaction identifier to web view, e.g. Ajax JSON response or JSP expression language.
When transaction data are successfully uploaded, we can start transaction itself. It can be done with use of Client API for Web Integration. We only need to specify ADUCID Binder methods to serve transaction:
aducid.setStartOperationUrl("/aducid-binder/transactionJson?transactionId=" + response.data); aducid.setResultOperationUrl("/aducid-binder/transactionCheck"); aducid.setProxyUrl("/aducid-binder/proxy");
Expression response.data
contains unique transaction identifier pushed from backend to view. After transaction run, user is redirected to redirectUrl
value (or to errorPage
if defined and error occurs).
User is now redirected to redirectUrl
, where we must process transaction operation result. Operation result is saved in HTTP request attributes. We try to read attribute with prefix AAA_UTR_
with transaction identifier at the end. When value exists, we must invoke base64 decoding on value to get readable JSON response.
See Transaction support, Positive response chapter.
See Transaction support, Negative response chapter.