Express Gateway v1.10.1 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more and brings the addition of a new policy and a small byproduct to our plugin framework that can potentially unleash new possibilities.
We have added a new policy called
oAuth2 introspection. This is particularly useful in case you're integrating Express Gateway with an external oAuth2 provider. Point your browser to our docs to know more. #747
We have added a new property to the
egContextobject that plugins can leverage:
requestStream. This can be useful in case you want to inject a custom body instead of proxying the original one to a
serviceEndpoint. We're planning to write a blog post containing some interesting use cases very soon. #763
When using Json Web Tokens for the oAuth2 policy, you'll now receive a
refresh_tokenthat you can use to grab a new access token. #758
We have reorganized our eslint plugins so that we're installing only the one we're using for real as well as configure them properly. #732
Express Gateway in production? Let us know!
As always, we're open to any feedback and ready to hear your story of putting Express Gateway in production. In case you're interested, please reach us on Gitter, via email or in any way you want.