On Fri, Dec 15, 2017 at 3:04 PM, Lakmal Warusawithana <[email protected]> wrote:
> Hi Susanka, > > On Fri, Dec 15, 2017 at 9:18 AM, Susankha Nirmala <[email protected]> > wrote: > >> Hi All, >> >> When we using APIM all in one active/active deployment pattern, by >> default gateway caching enabled and clustering disable according to the >> document [1], Due to that >> distributed caching is not use with this deployment pattern. With this >> deployment pattern, If we revoke a token, it will not update in both APIM >> nodes and in one APIM node same token will be available as a valid token. >> Due to that can we recommend this deployment architecture pattern in >> production environments? >> > > Its depends on customers requirement. Many cases, token revocation does > not need to revoke immediately (realtime). It will automatically revoke > when cache is expires. (eg 15 min) > With the default cache expiry time (15 minue) also we can access the API using revoked token until cache expire in other node.AFAIU onece we revoke a token, that token should be invalidate from the cache in all nodes. > > >> >> [1] - https://docs.wso2.com/display/AM210/Configuring+an+Active- >> Active+Deployment >> >> Thanks, >> /Susankha. >> >> >> >> -- >> Susankha Nirmala >> Senior Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> >> Mobile : +94 77 593 2146 <+94%2077%20593%202146> >> blog : https://susankhanirmala.wordpress.com/ >> > > > > -- > Lakmal Warusawithana > Senior Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 <+94%2071%20428%209692> > Blogs : https://medium.com/@lakwarus/ > http://lakmalsview.blogspot.com/ > > > -- Susankha Nirmala Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware Mobile : +94 77 593 2146 blog : https://susankhanirmala.wordpress.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
