You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 17, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: docs-new/auditbox/docs/api.md
+56-43Lines changed: 56 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,20 +12,25 @@ http://localhost:3002
12
12
13
13
## Authentication
14
14
15
-
Auditbox uses **Keycloak** for authentication and authorization. To access the FHIR API programmatically, you need to obtain a JWT access token from your Keycloak instance.
15
+
Auditbox uses **Keycloak** for authentication and authorization,
16
+
although any compliant OAuth2 identity provider (IDP) will work with
17
+
proper setup. To access the FHIR API programmatically, you need to
18
+
obtain a JWT access token from your IDP instance.
16
19
17
20
### Getting a Token from Keycloak
18
21
19
-
All FHIR API requests must include an `Authorization` header with a Bearer token issued by Keycloak:
22
+
All FHIR API requests must include an `Authorization` header
23
+
with a Bearer token issued by Keycloak:
20
24
21
25
```http
22
26
Authorization: Bearer <your-jwt-token>
23
27
```
24
28
25
-
To obtain a token from Keycloak, use the OAuth 2.0 client credentials or password grant flow. For example:
29
+
To obtain a token from Keycloak, use the OAuth 2.0 client credentials
30
+
or password grant flow. For example:
26
31
27
32
```bash
28
-
curl -X POST http://localhost:8888/realms/auditbox/protocol/openid-connect/token \
0 commit comments