Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/06/04 13:44
From version 42.1
edited by Waria
on 2026/06/04 12:08
Change comment: There is no comment for this version
To version 45.1
edited by Waria
on 2026/06/04 12:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -34,7 +34,7 @@
34 34  * Deploy agents can access the registry and can read the contents belonging to your eMagiz integration project only.
35 35  * Client runtimes can read specific flows within the registry as provided by the deploy agent to deploy the flows
36 36  * When running your eMagiz integration project in the cloud, security during communication between eMagiz and the registry is taken care of by the eMagiz cloud.
37 -* When running your eMagiz integration project on-premises, you will have to make sure that your server is running Docker and the eMagiz deploy agent so the server can access the registry successfully and securely. Learn more about this here: [[eMagiz Deploy Agent>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.emagiz-deploy-agent||target="blank"]]
37 +* When running your eMagiz integration project on-premises, you will have to make sure that your server is running Docker and the eMagiz deploy agent so the server can access the registry successfully and securely. Learn more about this here: [[eMagiz Deploy Agent>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-emagiz-deploy-agent||target="blank"]]
38 38  * A bitbucket pipeline can access the registry to update the provided base image that is needed to run all your flows. This pipeline cannot access your flows, only the libraries used to build your flows.
39 39  * Connections to the registry are always one-way SSL (encrypted) and all access is secured with a unique username/password combination.
40 40  * As mentioned above, the registry is read-only for agents and client runtimes. This means that even if someone gets their hands on a username/password combination, they do not have sufficient rights to alter anything in the registry. They can only read the data that is kept in the registry.