Hi Support, We are currently looking at utilizing Gluu Gateway 4.0 as a web proxy to provide user authentication and step-up authentication for backend applications. The authentication portion will be similar to the Apache mod_auth_openidc integration. In the Apache mod_auth_openidc, there is an option to pass claim as HTTP Header to the backend application. We understand that the Gluu Gateway 4.0 gluu-openid-connect plugin will pass the X-OpenId-Connect-userinfo JSON header to the backend, however, some COTS application will only consume simple HTTP header with simple parameters within (for example, uid or email in plaintext). Is it possible to configure the plugin to send additional HTTP headers in addition to the X-OpenId-Connect headers?