Regarding the method 1:
I am confused here.
. https://tyk.io/docs/tyk-dashboard-v1-0/endpoint-designer-plugins/url-rewriting/ I already have url-rewriting work with a hard-coded email address (which is obviously oblivious to the logged in user data).
For this, a consumer does not even have to come to the portal, as my request just go through the Tyk Gateway. I, the admin, just configure this entire thing through the portal, once and only once.
. https://tyk.io/docs/tyk-dashboard-v1-0/endpoint-designer-plugins/header-transforms/ suggests that we can transform the header with the user-specific data from LDAP such as user ID.
So, combining  & , what prevents getting the email address to the header during the re-write phase?
Probably I fail to understand why this is a post-processor, and how the "header injection would have already completed".
Regarding the method 2:
Please let me know where does the third-party (custom) app exist? is it a TIB or Gateway plugin, or something completely external as a separate entity?
I am puzzled that you recommend the method 2, while method 1 is the one that is discussed in the documentation (https://tyk.io/docs/tyk-dashboard-v1-0/endpoint-designer-plugins/header-transforms/)
Did I miss or misinterpret something?
Thanks a lot..