View Issue Details

IDProjectCategoryView StatusLast Update
0006427Talerlibeufin-bankpublic2023-09-23 13:09
ReporterMS Assigned ToMS Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritylowSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.9.3Fixed in Version0.9.3 
Summary0006427: EBICS errors need XML
DescriptionIn some (all?) error cases related to EBICS, the sandbox responds with plain text.
Instead it should respond with the XML document that complies to the EBICS specifications.
Additional InformationMoving to 0.2 because it became a testing problem.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

MS

2020-07-23 11:42

reporter   ~0016507

Last edited: 2020-07-23 11:44

Mostly addressed here: c716d23073be8846d0765fa766de341dbc953a88

MS

2020-07-23 11:48

reporter   ~0016508

The EbicsError global catcher needs a private key to be included in the exception object,
and if that's not found, it responds with JSON (and status 500). (The private key is needed
to sign the response object.)

The current problem is that not in all the parts of the code such private key is included in
the exception object, resulting still in JSON+500 being returned.

MS

2020-07-23 15:13

reporter   ~0016509

After private discussion, the private key will be moved away from the exception object. But at the same time, the exception handler
must be moved in a place where it is easier to get more context (including the private key) from the current request.

MS

2020-07-29 13:41

reporter   ~0016531

Fixed, but this test now fails: integration-tests/test-ebics-double-payment-submission.py

MS

2021-03-25 09:42

reporter   ~0017647

The test mentioned in the last comment was long ago removed, and in general, corner cases will 'all' have to be implemented in the new TypeScript harness. IMO, this can be closed.

Issue History

Date ModifiedUsernameFieldChange
2020-07-09 17:41MSNew Issue
2020-07-09 17:45MSDescription Updated
2020-07-23 11:42MSNote Added: 0016507
2020-07-23 11:44MSNote Edited: 0016507
2020-07-23 11:48MSNote Added: 0016508
2020-07-23 15:13MSNote Added: 0016509
2020-07-29 13:41MSNote Added: 0016531
2020-07-29 13:41MSAssigned To => MS
2020-07-29 13:41MSStatusnew => assigned
2020-11-10 11:15MSTarget Version => 0.9.1
2020-11-10 11:15MSAdditional Information Updated
2021-03-25 09:42MSNote Added: 0017647
2021-03-25 09:42MSPrioritylow => none
2023-01-08 09:36Christian GrothoffSeverityminor => feature
2023-01-08 09:36Christian GrothoffProduct Version => Git master
2023-01-08 09:36Christian GrothoffTarget Version0.9.1 => 0.9.3
2023-04-11 09:33MSStatusassigned => feedback
2023-04-11 09:34MSPrioritynone => low
2023-04-11 09:34MSTarget Version0.9.3 =>
2023-04-13 18:26Florian DoldCategorysandbox => libeufin sandbox
2023-04-13 18:38Florian DoldCategorylibeufin sandbox => libeufin-sandbox
2023-04-13 18:50Florian DoldProjectlibeufin => Taler
2023-04-17 09:04Florian DoldProduct VersionGit master =>
2023-04-17 09:04Florian DoldTarget Version => 0.9.3
2023-06-29 09:59MSStatusfeedback => informing
2023-06-29 09:59MSResolutionopen => fixed
2023-09-23 13:07Christian GrothoffFixed in Version => 0.9.3
2023-09-23 13:09Christian GrothoffStatusinforming => closed
2023-09-23 13:26Christian GrothoffCategorylibeufin-sandbox => libeufin-bank