Is it possible to configure TigerGraph so that when authorization on REST++ endpoints is enabled the server looks for the token in the HTTP request header somewhere other than in the “Authorization” header?
It’s a standard practice to include the token in this way. Authorization: Bearer <token> Can you elaborate a bit on the context which prompted you to ask the question?
The application that I’m developing is using a custom in-house developed framework and it appears that all HTTP requests are being intercepted by that framework and the value for ‘authentication’ in HTTP headers is being forced to a specific value and I can’t override it. This is probably being done to force all applications built on that framework to use a consistent authentication/security model. I can add custom HTTP headers just fine.