ubamrein
commented
4 years ago Hi!
The doumentation is a bit unprecise. I will update it accordingly.
Before the controller is executed, the @Valid annotations makes sure that the model is valid. The json you are providing is not valid, hence springboot rejects it with a 400 BadRequest.
The various validations are needed, since we want to guarantee a constant payload size for every request (so fake and real requests can't be distinguished, hence it is not easy to gather information on possible infected people by just looking at encrypted traffic).
So in your case there are for sure two mistakes:
1) The model for exposed should be a list of keys (plus some more properties) 2) The keys need to be a base64 encoding of 16 bytes (hence 24 characters)
For further validations please take a look at the models and what @Validation annotations they have.
For example GaenRequest:
public class GaenRequest {
@NotNull
@NotEmpty
@Valid
@Size(min = 14, max = 30)
@Documentation(description = "Between 14 and 30 Temporary Exposure Keys - zero or more of them might be fake keys. Starting with EN 1.5 it is possible that clients send more than 14 keys.")
private List<GaenKey> gaenKeys;
@NotNull
@Documentation(description = "Prior to version 1.5 Exposure Keys for the day of report weren't available (since they were still used throughout this day RPI=144), so the submission of the last key had to be delayed. This Unix timestamp in milliseconds specifies, which key date the last key (which will be submitted on the next day) will have. The backend then issues a JWT to allow the submission of this last key with specified key date. This should not be necessary after the Exposure Framework is able to send and handle keys with RollingPeriod < 144 (e.g. only valid until submission).")
private Integer delayedKeyDate;
public List<GaenKey> getGaenKeys() {
return this.gaenKeys;
}
public void setGaenKeys(List<GaenKey> gaenKeys) {
this.gaenKeys = gaenKeys;
}
public Integer getDelayedKeyDate() {
return this.delayedKeyDate;
}
public void setDelayedKeyDate(Integer delayedKeyDate) {
this.delayedKeyDate = delayedKeyDate;
}
}The models themselves should also provide a little bit more feedback to what each parameter means.
Regarding the demo, I can't quite follow what you mean.
We already provide two ways to test and give insights to how the backend is working:
1) You can use the apps and point them to your backend deployments 2) Have a look at the Test files which build the correct payloads
You are of course free to provide a PR adding some postman collections or similar. This is currently for us not high priority as we are preparing for multiple API changes coming in the future.
vijayakumarmariyappan
Try 1 Result:
Try 2 Result:
@ubamrein @martinalig
Thank you so much for your contribution to this project. You have provided demo for Android and iOS. That is good. But for Backend project found no clear steps to run. I'm sorry to say this.
I'm from Node JS platform. I can understand Java code as well. Somehow I did run the backend server by using the existing documentation. It runs. If I access the below API 1, then it responded with "Hello from DP3T WS". But for all other APIs, it returns 400 as status code. according to the documentation It says "Invalid base64 encoding in expose request". I really tried various input data inside body, but it always returns the same. Then I was thinking it has an issue in my jar file. Then I loaded "sdk.yaml" file in the path "/home/vijay/Desktop/dp3t-sdk-backend/documentation/yaml" in https://editor.swagger.io/.
I tried the below on that swagger editor, found that same behaviour as my local jar.
API 1: Request: GET http://localhost:8080/v1 OR https://demo.dpppt.org/v1 Response: Hello from DP3T WS
API 2: Request: POST http://localhost:8080/v1/exposed OR https://demo.dpppt.org/v1/exposed Body: { "key": "dGVzdA==", "keyDate": 1596672000, }
Here dGVzdA== is base64 encoded string of word "test". 1596672000 - timestamp is equivalent to 08/06/2020 @ 12:00am (UTC)- converted by https://www.unixtimestamp.com/index.php
Response: 400
I would like to know how can I use the backend app properly. is the below correct? First I'm storing the exposee's unique id(Example:email-id) in DB, by using this API(https://demo.dpppt.org/v1/exposed) Second I can get the list of friend who may have affected by his contact, by using https://demo.dpppt.org/v1/gaen/exposed/:timestamp
Did i do any mistakes on sending the data in the POST body? Kindly please help us regarding this. If you could add demo for backend, really really helpful to everyone. Thanks a lot :+1: