Re: [Dev] Revoked Access Token and Revoked Refresh Token returned back in token revoke endpoint response

On Tue, Nov 24, 2015 at 7:47 AM, Amila De Silva wrote: > Hi Sanjeewa, > > On Sunday, November 22, 2015, Sanjeewa Malalgoda > wrote: > >> 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

Re: [Dev] Revoked Access Token and Revoked Refresh Token returned back in token revoke endpoint response

Hi Sanjeewa, On Sunday, November 22, 2015, Sanjeewa Malalgoda wrote: > 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

Re: [Dev] Revoked Access Token and Revoked Refresh Token returned back in token revoke endpoint response

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

[Dev] Revoked Access Token and Revoked Refresh Token returned back in token revoke endpoint response

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