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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The metadata is openly accessible and is system instance aware.
41
41
Depending on the **tenant** the metadata return can potentially vary (reflecting customizations).
42
42
This strategy therefore only applies to multi-tenant systems.
43
43
44
-
When fetching metadata for a specific tenant, the request REQUIRES to add an additional HTTP Header `global-tenant-id` with a [CLD Tenant ID](https://wiki.one.int.sap/wiki/display/CLMAM/CLD+Tenant+ID) as a value.
44
+
When fetching metadata for a specific tenant, the request REQUIRES to add an additional HTTP Header `global-tenant-id` with a Tenant ID as a value (use value `740000101` for test purposes in this app).
45
45
The application internally maps from the global tenant ID to a local tenant and returns the metadata for the local tenant as requested (see [./src/data/user/tenantMapping.ts](./src/data/user/tenantMapping.ts)).
46
46
Therefore the application MUST support the mapping of the global tenant ID to its own tenant IDs.
47
47
@@ -54,7 +54,7 @@ In this case metadata would be returned without considering tenant specifics.
54
54
The metadata is openly accessible, but system instance aware.
55
55
Depending tenant the metadata that is return can vary (reflecting customizations).
56
56
57
-
When fetching metadata for a specific tenant, the request REQUIRES an additional HTTP Header `local-tenant-id` with a local tenant ID (that the application locally understands) as a value.
57
+
When fetching metadata for a specific tenant, the request REQUIRES an additional HTTP Header `local-tenant-id` with a local tenant ID (that the application locally understands) as a value (use value `T1` for test purpose in this app).
58
58
59
59
If the specified header is missing the request will be identical to the `open` access strategy.
60
60
Whether this is supported is defined by additionally supporting the `open` access strategy.
'No tenant ID provided in the request header via local-tenant-id or global-tenant-id. Hint: for demo purposes it can be set in the query string as well, e.g. ?local-tenant-id=T1',
0 commit comments