From 55de0d84ee23c87e7b55740b00370cb1f2cd6523 Mon Sep 17 00:00:00 2001 From: Marko Oldenburg Date: Sun, 28 Nov 2021 21:43:44 +0100 Subject: [PATCH] =?UTF-8?q?=E2=80=9EDocuments=20Bridge=20API=E2=80=9C=20?= =?UTF-8?q?=C3=A4ndern?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Documents-Bridge-API.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Documents-Bridge-API.md b/Documents-Bridge-API.md index 9ac9bf6..6fda592 100644 --- a/Documents-Bridge-API.md +++ b/Documents-Bridge-API.md @@ -69,4 +69,12 @@ We offer two ways of verifying calls to endpoints with a token: sha256("2019-03-05T01:06:53Z,4711,123456") = f52eb5ce382e356c4239f8fb4d0a87402bb95b7b3124f0762b806ad7d0d01cb6 -#### 3.2.2 Example calls \ No newline at end of file +#### 3.2.2 Example calls +**Plain token:** +http://192.168.1.50:8080/info?token=123456 + +**Hashed token:** +http://192.168.1.50:8080/info?ts=2019-03-05T01:06:53Z&rnr=4711&hash=f52eb5ce382e356c4239f8fb4d0a87402bb95b7b3124f0762b806ad7d0d01cb6 + +A hashed token will only be valid with a sufficiently current timestamp and can not be reused, to prevent replay attacks. So making two calls with the exact same timestamp will only work with different random numbers. +To debug problems with non synchronous times you can check the current time on the bridge via bridge discovery \ No newline at end of file