API Management
Microsoft Azure API Management is a turnkey solution for publishing APIs to external and internal consumers. Quickly create consistent and modern API gateways for existing backend services hosted anywhere, secure and protect them from abuse and overuse, and gain insights into usage and health. Plus, automate and scale developer onboarding to help get your API program up and running in no time.
-
We would like to have OWASP security features as part of API Management rather than using API gateway/WAF.
We would like to have OWASP security features as part of API Management rather than using API gateway/WAF.
139 votes -
A process for manually approving new users
Today, you have the possibility to force a manual process for approving a user access to a product. However, if you need to enable simple username-password you have no possibility to have a manual process for approving a user access to the portal.
It would be good for a user to see all products and APIs available in the portal, being able to browse and discover APIs. This means that anyone can create a user and browse APIs, basically spying on a company thru the names of APIs and products.
The other way is to hide all APIs behind Products…
26 votesThank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.
-
Add metadata to subscription
I would like the ability to add metadata to a subscription. A key-value that could describe the subscription.
Values should be accessible in policies - to be added as inbound headers for example.
The actual API could then use the values to return different values depending on the subscription.
16 votes -
Having the ability to
Having the ability to see which ciphers are active within the APIM. At the moment you can disable 3DES in the Portal and 9 other ciphers using a PATCH/PUT command but you cannot see which ciphers are actually active anywhere.
4 votesThank you for the feedback!
-
Ability to use certificate as secret for OAuth 2.o
OAuth 2.0 configuration has only option to provide secret. There is no option to provide certificate as secret. This is limiting our ability to use as our client id support only certificate secrete.
3 votesThank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.
- Don't see your idea?