Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/07/23 09:35
From version 55.1
edited by Waria
on 2026/06/23 11:43
Change comment: There is no comment for this version
To version 56.1
edited by Waria
on 2026/06/23 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,10 +22,10 @@
22 22  
23 23  eMagiz consists of various components communicating to develop the process layer and subsequently run the message layer as secure and stable as possible for our customers.
24 24  
25 +* In the eMagiz integration project, various flows are created that work together to realize the integration. The different types are shown on the top of the picture below.
26 +* 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).
27 +* 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).
25 25  
26 -1. In the eMagiz integration project, various flows are created that work together to realize the integration. The different types are shown on the top of the picture below.
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 -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 30  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--emagiz-architecture.png]]
31 31  
... ... @@ -167,7 +167,6 @@
167 167  This way, each connection between the application and the integration (end-point) can be adequately secured and gives the flexibility to confer with the external application which method suits their needs the best.
168 168  
169 169  ==== 3.5.2 API Gateway ====
170 -
171 171  To secure the front end of the API Gateway in eMagiz rights can be assigned to users in User Management. Users are automatically created for systems integrated by the API pattern in the Portal. Next to that manual users can be added for external systems that interact with the eMagiz API Gateway. You can configure read and write rights per created operation in your model. If a user has insufficient rights for the requested action, they will receive a 401 Unauthorized.
172 172  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.
173 173