We have a number of internal API's that are currently locked down using a relatively static and shared API key. We would like to expose these more broadly behind Tyk and use Tyk's built-in authentication mechanisms to give use finer grained API key's to new consumers that can be individually revoked. The problem is, Tyk doesn't appear to support authenticating itself against the downstream API. Am I mistaken on this? If not, is this something you have/might consider?

We have a number of internal API's that are currently locked down using a relatively static and shared API key. We would like to expose these more broadly behind Tyk and use Tyk's built-in authentication mechanisms to give use finer grained API key's to new consumers that can be individually revoked. The problem is, Tyk doesn't appear to support authenticating itself against the downstream API. Am I mistaken on this? If not, is this something you have/might consider?