How ABIS should process the Insert request with data share URL?
MOSIP when wants to insert a biometric record in ABIS, it shares the insert request over the MOSIP-to-ABIS queue which contains the data share URL. In order to get data out of this URL, the ABIS needs to get the authentication token from MOSIP’s auth manager. Here are some of the rules that should be followed by the ABIS in their implementation when calling the authentication manager.
Expected Process Flow
Rules
Here are some of the basic thumb rules that should be followed.
Request for new authentication token only when the token has expired, is not available or the data share sends the error code as
KER-AUTH-401
andKER-AUTH-003
.{ "id": null, "version": null, "responsetime": "2021-02-05T06:29:48.257Z", "metadata": null, "response": null, "errors": [ { "errorCode": "KER-ATH-401", "message": "Authentication Failed" } ] }
For all other error codes received from the data share like
DAT-SER-003
andDAT-SER-006
share the failure code as 17.The response code for failures in MOSIP for all APIs is
200
. Standard failure response codes such as404
or50X
, should also be handled appropriately.Auth Manager should be called by ABIS only to generate an authentication token, not to validate the authentication token.
For more information about the request and response structure of Insert and Identify request as well as data share encryption, please follow our page, on ABIS APIs.