我需要设计一个单个平台，以登上项目中不同团队来管理REST API的所有API网关。现在，这里的挑战是，每个API网关都会有自己提供安全性的方式，例如，Akamai Gateway提供客户秘密＆amp;客户ID到消费者＆amp;消费者必须击中一个单独的URL，以获取JWT安全令牌，该标记最终通过将JWT令牌发送到标题中来触发实际的API。 Apigee或Kong的类似方式将有自己的方式提供安全性＆amp;他们可能只需要一个API密钥作为安全令牌即可。另外，为任何REST API完成的网关设置需要IP地址的白色。在开发单个平台门户网站时，我该如何管理所有这些。确保订阅或JWT令牌从API网关无缝浮动到我们的主要平台门户...基本上，我正在寻找架构＆amp;我应该使用哪些软件工具来开发此功能。它基本上将充当母亲门户，该门户将与不同的API网关＆amp;它将为REST API消费者提供服务。生产者。
I have a requirement to design a single platform to onboard all the API gateways which are being used by different teams within the project to manage the REST APIs. Now, the challenge here is that every API gateway will have its own way of providing security, for example, the Akamai gateway provides client secret & client-id to the consumer & consumer has to hit a separate URL in order to get the JWT security token which is being used to finally hit the actual API by sending the JWT token in the header. Similar way Apigee or KONG will have their own way of providing the security & it might happen that they only need an API key as a security token. Also, the gateway setup done for any REST API requires the whitelisting of IP addresses. How can I manage all this while developing a single platform portal & make sure that subscription or JWT token is floating seamlessly from the API gateway to our main platform portal... Basically, I'm looking for architecture & what software tools should I use to develop this. It will basically act as a mother portal that will internally connect with different API gateways & it will serve both the REST API consumers & producers.
发布评论
评论（1）
在这里的建议，因为这不是一个客观的问题，有一个特别可验证的答案：首先，努力将组织的API管理工具标准化。您是Kong商店还是Apigee商店？如果有标准，那么优化您的门户用例和围绕该标准的集成要求将比“许多孤岛”案例容易。无论如何，关键是利用APIM堆栈的管理API直接集成。 Apigee通过对基于Drupal的门户的长期支持，以其
Advice here, as this isn't an objective question with a particularly verifiable answer: First, work to standardize what is your organization's API-Management tooling. Are you a Kong shop, or an Apigee shop? If there is a standard, then optimizing your portal use-cases and integration requirements around that standard will be easier than the "many siloes" case. In any case, the key is to leverage the APIM stacks' management APIs to directly integrate. Apigee makes this easy via their long-term support for Drupal-based portals, in the form of their Apigee Developer Portal Kickstart Drupal distribution