Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Dokumentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
FIT-Connect
Dokumentation
Merge requests
!196
Callback um Destination-ID ergänzen
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Callback um Destination-ID ergänzen
301-add-destination-id-to-callbacks
into
main
Overview
3
Commits
2
Pipelines
0
Changes
2
Merged
Michael Miera
requested to merge
301-add-destination-id-to-callbacks
into
main
2 years ago
Overview
3
Commits
2
Pipelines
0
Changes
2
Expand
planning#301 (closed)
0
0
Merge request reports
Compare
main
version 5
5200030f
2 years ago
version 4
72517ad8
2 years ago
version 3
cd184e10
2 years ago
version 2
1b19e9ab
2 years ago
version 1
966edb7c
2 years ago
main (base)
and
latest version
latest version
c8386387
2 commits,
2 years ago
version 5
5200030f
2 commits,
2 years ago
version 4
72517ad8
2 commits,
2 years ago
version 3
cd184e10
2 commits,
2 years ago
version 2
1b19e9ab
2 commits,
2 years ago
version 1
966edb7c
2 commits,
2 years ago
2 files
+
28
−
6
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
Files
2
Search (e.g. *.vue) (Ctrl+P)
docs/details/callbacks.mdx
+
14
−
3
Options
@@ -97,13 +97,24 @@ Um [Replay-Angriffe](https://de.wikipedia.org/wiki/Replay-Angriff) zu vermeiden,
Dieser Timestamp wird im HTTP-Header `callback-timestamp` übertragen.
Bei der Prüfung der Echtheit des ausgelösten Callbacks **MÜSSEN** API-Clients prüfen, dass der angegebene Timestamp nicht älter als **5 Minuten** ist.
Das folgende Beispiel zeigt die Verwendung der HTTP-Header `callback-authentication` und `callback-timestamp`:
Das folgende Beispiel zeigt die Verwendung der HTTP-Header `callback-authentication` und `callback-timestamp`.
Zu beachten ist, dass das Feld `submissionIds` als *deprecated* markiert wurde und durch das Feld `submissions` ersetzt werden soll.
```http
POST /callbacks/fit-connect
callback-authentication:
798cd0edb70c08e5b32aa8a18cbbc8ff6b3078c51af6d011ff4e32e470c746234fc4314821fe5185264b029e962bd37de33f3b9fc5f1a93c40ce6672845e9
0df
callback-authentication:
2056b372b5bcec06d8f11ab79b84b42d6cbe1c8e1178cdfa36e4385dcf717758aaa7599f417d9ec3e079087884f4fd59680bf713621383e2d4414ef74fb1
0df
3
callback-timestamp: 1672527599
{"type":"https://schema.fitko.de/fit-connect/submission-api/callbacks/new-submissions","submissionIds":["f39ab143-d91a-474a-b69f-b00f1a1873c2"]}
{
"type":"https://schema.fitko.de/fit-connect/submission-api/callbacks/new-submissions",
"submissionIds":["f39ab143-d91a-474a-b69f-b00f1a1873c2"],
"submissions":[
{
"destinationId":"d12caea8-f372-4eb1-b102-b0a228253a11",
"submissionId":"f39ab143-d91a-474a-b69f-b00f1a1873c2",
"caseId":"9eec7d3e-dc66-4f82-9f52-1520bf96a32e"
}
]
}
```
Der HMAC wird gebildet aus dem im HTTP-Header `callback-timestamp` übertragenen Zeitstempel und dem im HTTP-Body übertragenen Payload, getrennt durch das Zeichen `.` (Punkt), jeweils UTF-8-kodiert. Der HMAC wird hexadezimal kodiert übertragen.
Loading