Skip to Content
Last modified by Waria on 2026/07/23 10:17
From version 18.1
edited by Erik Bakker
on 2024/09/03 08:20
Change comment: There is no comment for this version
To version 19.1
edited by Waria
on 2026/07/23 10:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.waria
Content
... ... @@ -37,8 +37,8 @@
37 37   ** For an API Gateway, the requestor needs to be able to call a REST based webservice using a supported messaging format
38 38   ** Messaging allows other web services such as SOAP, but can also handle XML for instance
39 39  * **Centralized User Management**
40 - ** API gateway offers a easy to configure user management capability to protect operations. Users and roles can be designed in the Design phase, and various authentication methods are allowed such as OAuth2.0 and API Keys. eMagiz offers easy to use configurations for that
41 - ** For Messaging, no such user management options exit and all needs to be created inside the flows that handle the requests & replies.
40 + ** API gateway offers straightforward user management to protect operations. Users can be designed in the Design phase, and various authentication methods are allowed such as OAuth 2.0, Basic Auth and API Keys. eMagiz offers easy to use configurations for that.
41 + ** For Messaging, no such user management options exist and all needs to be created manually inside the flows that handle the requests & replies.
42 42  
43 43  == 4. Key takeaways ==
44 44