API Access ( as described here): Users will not be able to use SAP Cloud Platform API Management APIs to directly create and manage API artifacts on API Management. However, users will have UI access to work with the API artifacts. API Access shall be enabled by Q2 2020.
Op-Proxy(as described here): Users will not be able to create API Providers of type On-Premise to seamlessly connect to their On-premise backends via the Cloud Connector. However, they can still manage services from their on-premise back-ends by opening access using a reverse proxy. On-premise API Provider support shall be enabled by Q1 2020.
ACL for products(as described here) : Users will not be able to define custom roles for discovery and subscription of products. Support for such custom role definition shall be enabled by Q1 2020.
Client SDK(as described here): Users will not be able to use Client SDK for SAP API Management to integrate into their CI/CD pipelines. Support for the Client SDK shall be enabled by Q2 2020.
Multiple VH(as described here): Users will not be able to create multiple virtual hosts in a single sub-account/organization that is used in their API artifacts. This shall be enabled by Q2 2020.
Route service binding support(as described here): Users will not be able to automatically attach this instance of API Management as their route service using the convenience of ‘preview’ plan. However, this can be done using a user-provided service. This shall be enabled by Q1 2020.
Notifications during Developer Onboarding(as described here): Administrators will be notified via preconfigured e-mail when developers request access to Developer Portal. Similarly, developers will be notified via preconfigured email when their request gets approved or rejected. Email Configuration in the developer portal feature is not enabled. However, the Developer Portal UI gives visibility on the access status of email configuration. The complete mail notification feature shall be enabled by Q1 2020.
Automated on-boarding: Users will not be able to on-board the API Portal service in a fully automated form. They need to reach out to Operations to complete the provisioning. Fully automated onboarding shall be enabled in Q1 2020.
Create an API for an Integration Flow(as described here): Users will not be able to create an API Provider of type “Cloud Platform Integration” to connect to a Cloud Platform Integration system, discover Integration Flows through the API Provider and generate APIs for the same. The complete feature shall be enabled by Q2 2020.
Disclaimer : This document and SAP’s strategy and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. All forward
-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations.
SAP Cloud Platform API Management in Cloud Foundry ( Amazon Web Service, Microsoft Azure, SAP NS2)
API Managment, CF, Azure, AWS , KBA , OPU-API-OD , On Demand , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.