-
|
Hi all, looking for some help on how to attach a custom tool such as a user interface or dashboard to a Guardian instance. When I look at our Guardian instance, it seems like this functionality would reside in the container "guardian-api-gateway". But in the current docker-compose setup, that container's port isn't forwarded which seems to indicate you're not supposed to use the container that way. I could obviously modify the docker-compose file. An alternative to me seems to directly connect to the mogodb and retrieve data from there. But that probably will not be a manageable situation in a production scenario. Could anyone point me to resources on how to set this up in the recommended way? Maybe people have experience setting up something similar? Thanks! Bram |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Hi @bbosch-d , the supported way would be to deploy your UI in your own container and use Guardian API to access data/info. Please see the docs for example starting point here or here. And in the locally running Guardian instance http://localhost:3000/api-docs/v1/ |
Beta Was this translation helpful? Give feedback.
-
|
Hi @anvabr thanks for your answer! You seem to have linked an open github issue instead of the docs. I'm not sure if that was intentional.
I'm correctly assuming the Guardian API runs in the "guardian-api-gateway" docker image if I use the docker compose setup? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, yes the link is corrected now! |
Beta Was this translation helpful? Give feedback.
-
|
Alright so it seems the API just runs on the web-proxy container. Swagger is also there: Then to log in, first get a refreshToken (/api/v1/accounts/login/) and then convert that to an access token (/api/v1/accounts/access-token/). In a test environment, you can simply log in as the default "Standard Registry" with a standard password. |
Beta Was this translation helpful? Give feedback.
Alright so it seems the API just runs on the web-proxy container. Swagger is also there:
<your host>/api/v1/api-docsThen to log in, first get a refreshToken (/api/v1/accounts/login/) and then convert that to an access token (/api/v1/accounts/access-token/).
In a test environment, you can simply log in as the default "Standard Registry" with a standard password.
See here: https://docs.hedera.com/guardian/guardian/users/user-operations/account-apis/authentication-process