Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/07/23 09:35
From version 52.1
edited by Waria
on 2026/06/04 13:30
Change comment: There is no comment for this version
To version 54.1
edited by Waria
on 2026/06/23 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -27,8 +27,8 @@
27 27  2. Your customized flows are combined with a base image (which contains framework components to make the flows work) and are deployed into a runtime (java-based application container).
28 28  3. These runtimes run on Cloud machines that contain Cloud templates (all required components to make the Cloud machine operational such as OS, Java runtime version, and more).
29 29  
30 +[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--emagiz-architecture.png]]
30 30  
31 -
32 32  Your flows are stored within a registry so deployments can be managed efficiently. To prevent unauthorized access to this repository, the following measures have been taken:
33 33  
34 34  
... ... @@ -40,8 +40,6 @@
40 40  * Connections to the registry are always one-way SSL (encrypted) and all access is secured with a unique username/password combination.
41 41  * 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.
42 42  
43 -
44 -[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--emagiz-architecture.png]]
45 45  
46 46  === 3.2 Security Guidelines - Cloud ===
47 47  
... ... @@ -170,7 +170,7 @@
170 170  
171 171  ==== 3.5.2 API Gateway ====
172 172  
173 -A structure with roles and rights per role can be specified within the portal or via an external IDP to secure the front end of the API Gateway in eMagiz. For the backend of the API Gateway, the same logic applies as stated above for messaging, which means that eMagiz supports the industry standard. Therefore, you as a user should confer with the external party about the correct method.
171 +A structure with roles and rights per role can be specified within the portal to secure the front end of the API Gateway in eMagiz. For the backend of the API Gateway, the same logic applies as stated above for messaging, which means that eMagiz supports the industry standard. Therefore, you as a user should confer with the external party about the correct method.
174 174  
175 175  ===== 3.5.2.1 Portal =====
176 176