ADUCID 4.x

User Tools

Site Tools

Trace:
nocode:transactions

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
nocode:transactions [2019/08/13 05:12]
740803864 [Negative response] 		nocode:transactions [2019/08/13 05:47]
740803864
Line 16: Line 16:
 | udi | String | No | if defined, security attack check is realized | | udi | String | No | if defined, security attack check is realized |
 | peigId | String | No | if defined, mobile push notification is realized | | peigId | String | No | if defined, mobile push notification is realized |
-**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).+**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. We must also remember to provide generated transaction identifier to web view, e.g. Ajax JSON response or JSP expression language.
Line 63: Line 63:
 </code> </code>
  
-In case of AIM failure, values ''statusAIM'' and ''statusAuth'' will be filled, ''statusLF'' only in case of personal code use. You can find ''statusAuth'' and ''statusLF'' meanings in chapter [[other:error-statuses|Error statuses of authentication process]]. Meanings of ''statusAIM'' can be found in[[other:aim-statuses|Semantics of individual statuses of the authentication session (AIMStatus)]] chapter. Attribute ''message'' is technical readable text describing error.+In case of AIM failure, values ''statusAIM'' and ''statusAuth'' will be filled, ''statusLF'' only in case of personal code use. You can find ''statusAuth'' and ''statusLF'' meanings in chapter [[other:error-statuses|Error statuses of authentication process]]. Meanings of ''statusAIM'' can be found in [[other:aim-statuses|Semantics of individual statuses of the authentication session (AIMStatus)]] chapter. Attribute ''message'' is technical readable text describing error.
  
 Secondary level failure can look like: Secondary level failure can look like:
nocode/transactions.txt · Last modified: 2020/03/29 11:34 by 77.75.78.163

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki