Hi All,

As in the previous APIM versions, there were 4 ways to block an
API/Subscription.

*1. Block an API using API lifecycle "Blocked" state*

API owner can block an API in publisher using API lifecycle. This will
temporarily block an API and can be promoted to "Published" state again.



*2. Block a subscription*
Publisher can block subscriptions using manage subscription. This can be
used to block an app in Production level or in both Production and Sandbox
levels.



*3. Throttle level blocking*
An specific endpoint can be blocked by setting Production and Sandbox TPS to
0 in publisher .



*4. Block an API using Admin dashboard*An API can be blocked using Black
List feature in Admin dashboard.

As per discussion within the team, we came to a conclusion to remove the
"Blocked" state from API lifecycle which is used to block an API, since it
is an edge case where API owner blocks his own API in publisher. If an API
needs to be blocked it can be done using 2,3 or 4.

Please share your thoughts on this.

Regards,
Yasima.

-- 
http://wso2.com/signatureYasima Dewmini
Software Engineer, WSO2, Inc.
Email: [email protected]
Mobile: +94713117081 <+94%2071%20311%207081>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to