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
* add support for optional swagger ui
[ci]
Signed-off-by: Peter Kvokacka <peter.kvokacka@digitalasset.com>
* [ci]
Signed-off-by: Peter Kvokacka <peter.kvokacka@digitalasset.com>
* [ci]
Signed-off-by: Peter Kvokacka <peter.kvokacka@digitalasset.com>
---------
Signed-off-by: Peter Kvokacka <peter.kvokacka@digitalasset.com>
Copy file name to clipboardExpand all lines: cluster/compose/localnet/README.md
+36-1Lines changed: 36 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,18 @@ The `*.localhost` domains will resolve to your local host IP `127.0.0.1`.
86
86
-**App Provider**: app-provider
87
87
-**SV**: sv
88
88
89
+
## Swagger UI
90
+
91
+
When the `swagger-ui` profile is enabled, the Swagger UI for the `JSON Ledger API HTTP Endpoints` across all running participants is available at [http://localhost:9090](http://localhost:9090).
92
+
Note: Some endpoints require a JWT token when using the **Try it out** feature. One method to obtain this token is via the Canton Console. Start the Canton Console and execute the following command:
93
+
```
94
+
app-provider.adminToken
95
+
```
96
+
97
+
For proper functionality, Swagger UI relies on a localhost nginx proxy for `canton.localhost` configured for each participant. For example, the `JSON Ledger API HTTP Endpoints` for the app-provider
98
+
can be accessed at the nginx proxy URL `http://canton.localhost:${APP_PROVIDER_UI_PORT}` via Swagger UI, which corresponds to accessing `localhost:3${PARTICIPANT_JSON_API_PORT}` directly.
99
+
The nginx proxy only adds additional headers to resolve CORS issues within Swagger UI.
0 commit comments