Skip to content

Commit

Permalink
Clarify that all APIs are supported
Browse files Browse the repository at this point in the history
Signed-off-by: James Rhodes <[email protected]>
  • Loading branch information
jarhodes314 committed Oct 13, 2023
1 parent 112518a commit cfba699
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions docs/src/references/tedge-cumulocity-proxy.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ configuration

For example, you can access the current tenant information
at [http://127.0.0.1:8001/c8y/tenant/currentTenant](http://127.0.0.1:8001/c8y/tenant/currentTenant)
from the machine running `tedge-mapper`. The server supports all possible request methods (
e.g. `HEAD`/`GET`/`PUT`/`PATCH`/`DELETE`).
from the machine running `tedge-mapper`.
The server supports all public REST APIs of Cumulocity, and all possible request methods
(e.g. `HEAD`/`GET`/`PUT`/`PATCH`/`DELETE`).
There is no need to provide an `Authorization` header (or any other authentication method) when accessing the API.
If an `Authorization` header is provided, this will be used to authenticate the request instead of the device JWT.

Expand Down

0 comments on commit cfba699

Please sign in to comment.