View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005947||libeufin||sandbox||public||2019-10-24 20:13||2019-10-25 14:58|
|Reporter||Marcello Stanisci||Assigned To|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0005947: Design generation of "OrderID"|
|Description||The element "ebicsKeyManagementResponse/header/mutable/orderID" is currently set to a mock value, but it must contain a meaningful identificator.|
|Additional Information||The responsible object is generated in KeyManagementResponse.kt.|
|Tags||No tags attached.|
See "Order Number" in the glossary (https://docs.taler.net/libeufin/ebics.html#ebics-glossary) for more info about the order ID.
The number must be unique per subscriber and order type. I'd suggest keeping a counter per subscriber and incrementing that in the same (SQL) transaction where the (EBICS) transaction is created.
Also, there needs to be some additional logic to "recycle" order IDs, since the space of order IDs is very small.
An order ID can be reused if the corresponding order is completely processed (e.g., there are no pending VEUs).