Hi Paul,
On 5 July 2013 13:47, Paul Fremantle <[email protected]> wrote: > Agreed. > > We also need to support having ONLY a sandbox and no production endpoint > for beta or early access to new APIs. > +1. May be we can add a new API life cycle status, which publishes the API to the store, but allows only SANDBOX access. Will add this to redmine. Thanks, Lakmali Paul > > > On 5 July 2013 08:22, 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. >> >> Thanks, >> Lakmali >> >> -- >> Lakmali Baminiwatta* >> * >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 71 2335936 >> blog : lakmali.com >> * >> * >> > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > -- 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
