Along with 2-way-SSL setup for authentication in TDV, need to pass user id from client to make it use for authorization in TDV

 Requirement:

TDV oData Services are exposed via API Gateway platform. In order to have secure authentication between API Gateway and TDV, we want to implement 2-way-SSL (i.e. mutual authentication) so that none of other system can directly call the TDV oData services directly.

Along with that we need to also enable authorization on TDV based on consumer is calling oData service via API Gateway platform. To achieve same, we want to pass the consumer user ID in HTTPS Header along with 2-way-SSL on TDV.

So that after 2-way-SSL based authentication in TDV, TDV platform can use User ID for authorization (e.g. for oData Service access, row or column level authorization, etc.)