Skip to Content

Changes for page eMagiz API Gateway

Last modified by Waria on 2026/07/23 10:26
From version 53.1
edited by Waria
on 2026/07/23 10:26
Change comment: There is no comment for this version
To version 52.1
edited by Erik Bakker
on 2026/01/02 10:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.waria
1 +XWiki.ebakker
Content
... ... @@ -11,7 +11,7 @@
11 11  
12 12  == 3. Introducing API Gateway ==
13 13  
14 -The eMagiz API Gateway is the pattern in which a specific entry point is made available for external applications (users). These external applications can connect to this entry point via a series of operations. These operations are listed in a manner that allows this application user to retrieve data or provide data. Users are managed on a central level to control access to the various data sources.
14 +The eMagiz API Gateway is the pattern in which a specific entry point is made available for external applications (users). These external applications can connect to this entry point via a series of operations. These operations are listed in a manner that allows this application user to retrieve data or provide data. Users & Roles are managed on a central level to control access to the various data sources.
15 15  
16 16  [[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-1.png]]
17 17  
... ... @@ -40,9 +40,9 @@
40 40  eMagiz does allow to influence some of these response codes by specific information per HTTP responses codes. Or provide custom responses.
41 41  
42 42  === 3.5 Centralized User Management ===
43 -In the context of an API Gateway, user management is the mechanism whereby users (i.e. external systems) are granted permissions to a specific set of operations on your API Gateway. The user gets credentials from eMagiz to access the API Gateway. Whenever a user calls your API Gateway, eMagiz evaluates if the user is allowed to access your API Gateway (authentication) and if the user has the rights to the specific operation they are calling (authorization). In this way, the access to the gateway is handled centrally.
43 +In the context of an API Gateway, user management means the mechanism whereby users are granted access to a specific set of operations. User Management in eMagiz can define users and roles. The user will have the access credentials to access the API Gateway in the first place. Options are OAuth2.0 or API Key. Users are assigned a role that defines to what operations access has been given. In this way, the access to the gateway is handled centrally, and the data exposed is adequately protected. Credentials are to be submitted to application users on a separate note.
44 44  
45 -=== 3.6 API Discovery ===
45 +=== 3.6 API Disovery ===
46 46  External application users can discover the operations via an online Portal * the SwaggerUI technology is used for that purpose. In that online section, the user can see all the published operations. For operation, all the required information is displayed to understand how to connect to the API correctly. That includes the request and response definitions, parameters, naming, response codes, and many more. Once the credentials have been provided, the application user can try out the operation.
47 47  
48 48  [[image:Main.Images.Fundamental.WebHome@fundamental-api-gateway-introduction-3.png]]