In 1.10 we have commemted out cache clear handler in revoke api but it was there in token API. So by default we will not use transport headers coming from revoke request but use in token api. But i dont see any other option if we need to clear cache in gateway. @amila have we done something to clear cache without cache clear handler?
if not we have 2 options 1. clear cache during request path of token revoke apis. Then we can clear cache without relying on what happen in key manager side. Disadvantage of this is we have to build message body in request path. 2.Have extension point in key manager to register call back for token revoke events. Then we can implement code to call back to gateway. WDYT? Thanks sanjeewa. sent from my phone On Nov 23, 2015 12:38 AM, "Johann Nallathamby" <[email protected]> wrote: > APIM Team, > > Regarding [1], I know this was implemented as part of a requirement for > API Manager. Does API Manager rely on this still ? Can we get rid of > returning these tokens ? In the new versions of API Manager if you are > supporting external key managers according to standards how are you going > to interoperate if you relying on such custom headers ? > > [1] https://wso2.org/jira/browse/IDENTITY-4112 > > -- > Thanks & Regards, > > *Johann Dilantha Nallathamby* > Technical Lead & Product Lead of WSO2 Identity Server > Governance Technologies Team > WSO2, Inc. > lean.enterprise.middleware > > Mobile - *+94777776950* > Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>* >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
