post-management-wire-disable.rst (1608B)
1 .. http:post:: /management/wire/disable 2 3 This request will be used to disable the use of the given wire method. 4 We use POST instead of DELETE because the exchange will retain state 5 about the wire method (specifically the end date) to prevent replay 6 attacks abusing the `WireSetupMessage`. Also, DELETE would not 7 support a body, which is needed to provide the signature authorizing 8 the operation. 9 10 **Request:** 11 12 The request must be a `WireTeardownMessage`. 13 14 **Response:** 15 16 :http:statuscode:`204 No content`: 17 The auditor has successfully disabled the wire method. The body is empty. 18 :http:statuscode:`403 Forbidden`: 19 The signature is invalid. 20 :http:statuscode:`404 Not found`: 21 The wire method is unknown to the exchange. 22 :http:statuscode:`409 Conflict`: 23 The exchange has a more recent request related to this wire method (replay detected). 24 25 **Details:** 26 27 .. ts:def:: WireTeardownMessage 28 29 interface WireTeardownMessage { 30 31 // Full ``payto://`` URL identifying the account and wire method 32 payto_uri: string; 33 34 // Signature using the exchange's offline key over a 35 // `TALER_MasterDelWirePS`. 36 // with purpose ``TALER_SIGNATURE_MASTER_WIRE_DEL``. 37 master_sig_del: EddsaSignature; 38 39 // Should be the time when the signature was created, 40 // using the (monotonic!) local time of the system 41 // with the offline master public key. Note that 42 // even if the time is in the future, the wire method will 43 // become inactive immediately! Used ONLY to detect replay attacks. 44 validity_end: Timestamp; 45 46 }