View Issue Details

IDProjectCategoryView StatusLast Update
0008759Talerchallengerpublic2024-08-28 21:30
Reportersebasjm Assigned Tosebasjm 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
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version0.11 
Target Version0.13Fixed in Version0.13 
Summary0008759: implement spec v2
Descriptionchanges:

* added address_type in /config (spa right now doesn't know which addr_type backend is expecting, defaulting to email)
* moved restrictions to /config (since it will not change based on challenge)
* added challenge status info: (so SPA can show better info of the challenge status when the page is loaded)
 - added retransmission_time with type Timestamp
 - added pin_transmissions_left
 - added auth_attempts_left
* prevent 302 when request type is application/json (in /challenge and /solve because of https://fetch.spec.whatwg.org/#atomic-http-redirect-handling )
* support application/json for request

 * deprecating next_tx_time in ChallengeCreateResponse in favor of retransmission_time in ChallengeStatus

NOT IN THE SPEC

 * we should have a request interface for application/json, right now challenger SPA is sending {"email":"..."} (and it works) but docs ask for {"adress":"..."}

> The posted form data must contain an “address”.

for endpoints:
 - https://docs.taler.net/core/api-challenger.html#post--token
 - https://docs.taler.net/core/api-challenger.html#post--solve-$NONCE
 - https://docs.taler.net/core/api-challenger.html#post--challenge-$NONCE


TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

child of 0008556 closedsebasjm implement restricting phone numbers to +41 
child of 0008731 closedsebasjm create spec for get challenge information and solved them 
child of 0008405 closedsebasjm invalid-pin form needs to show user proper choices 

Activities

sebasjm

2024-07-01 18:29

developer   ~0022776

4d657c2e055a93a5dc94300841379e037b84d006

Issue History

Date ModifiedUsernameFieldChange
2024-04-22 16:55sebasjmNew Issue
2024-04-22 16:55sebasjmStatusnew => assigned
2024-04-22 16:55sebasjmAssigned To => Christian Grothoff
2024-04-22 16:57sebasjmDescription Updated
2024-04-22 17:00sebasjmDescription Updated
2024-04-22 17:19sebasjmRelationship addedchild of 0008556
2024-04-22 17:21sebasjmRelationship addedchild of 0008731
2024-04-22 17:21sebasjmRelationship addedchild of 0008405
2024-05-05 13:41Christian GrothoffTarget Version0.11 => 0.14
2024-05-13 19:19Christian GrothoffTarget Version0.14 => 0.13
2024-07-01 18:02sebasjmAssigned ToChristian Grothoff => sebasjm
2024-07-01 18:29sebasjmStatusassigned => informing
2024-07-01 18:29sebasjmResolutionopen => fixed
2024-07-01 18:29sebasjmNote Added: 0022776
2024-08-26 20:30Christian GrothoffFixed in Version => 0.13
2024-08-28 21:30Christian GrothoffStatusinforming => closed