Skip to content

Commit b8b2a6d

Browse files
authored
Clarifying management API authentication
Added a note with the client_id, that you need to leave the client_secret empty for non-production environments as it's easy to miss the hint below the screen shot that lets you know that you need to leave the client_secret empty.
1 parent ffe8e45 commit b8b2a6d

File tree

1 file changed

+1
-1
lines changed
  • 14/umbraco-cms/reference/management-api

1 file changed

+1
-1
lines changed

14/umbraco-cms/reference/management-api/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ You can see an example of how to connect a backoffice user via OAuth2 in Postman
4848

4949
To test a Management API endpoint, follow these steps:
5050

51-
1. Authenticate via the **Authorize** button. Make sure you use `umbraco-swagger` as the `client_id`:
51+
1. Authenticate via the **Authorize** button. Make sure you use `umbraco-swagger` as the `client_id` and in non-production environments you need to leave the `client_secret` blank:
5252

5353
![Umbraco Management API when Authenticated](../images/management-api-swagger-authenticated.png)
5454

0 commit comments

Comments
 (0)