„Documents Bridge API“ ändern
@ -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
|
||||
#### 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
|
Reference in New Issue
Block a user