Hi,
On 8 July 2013 15:51, Lalaji Sureshika <[email protected]> wrote: > Hi Lakmali, > > > On Fri, Jul 5, 2013 at 12:22 AM, Lakmali Baminiwatta <[email protected]>wrote: > >> >> Hi all, >> >> In API Manager, the API creator can block a particular subscription on >> an API to disable access to it until s/he decides to unblock it again. With >> this blocking, both production and sandox invocations with that >> subscription is blocked. But there can be situations where there is a >> broken app. Then while fixing it, access to sandbox is needed to test the >> subscription. Therefore this improvement is suggested to block only the >> production access. >> >> Currently in APIM we keep Subscription Status (SUB_STATUS) for a >> subscription, which is set as BLOCKED once the subscription is blocked. >> Then in an API call, while doing the key validation it checks the >> SUB_STATUS for the subscription related to that key and blocks the call if >> it was in BLOCKED state. So what we can do here is, do the blocking if the >> Key Type is Production only. >> >> Any concerns, thoughts are welcome. >> > > I have a question..The above improvement will be added to publisher > app,while keeping current subscription blocking functionality [block both > production and sandbox accessing] as it is..right? > No. Actually I was going to make the subscription blocking functionality to do the production access blcoking only. So always the Sandbox key is not blocked. But +1 for this. Will keep the current subscription blocking functionality as well. So then there will be two blocking options support from publisher UI > [either to block whole subscription or allow only sandbox accessing] > Yes. So we will need add two options which does production access block and whole access block. > and when doing key validation,you need to consider those two options as > well..[May be you need to add additional SUB_STATUS type for this > requirement..] > Yes, We need to have another subscription status which captures production only blocked state. Thanks for the suggestions. Will work on these. Thanks, Lakmali > > Thanks; > > >> >> Thanks, >> Lakmali >> >> -- >> Lakmali Baminiwatta* >> * >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.com >> * >> * >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Lalaji Sureshika > WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +94 71 608 6811 > blog: http://lalajisureshika.blogspot.com > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Lakmali Baminiwatta* * Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
