I use a SaaS product with it's own API over which I have no control.
To obtain the authorization token I do a POST request with username and password in the body, and the token is in the response HEADER, rather than body. This token is then used for all other API requests.
This works fine in Postman, as per below: -
HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: text/html
Content-Encoding: gzip
Expires: -1
Vary: Accept-Encoding
Authorization: a<redacted>z
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
Access-Control-Expose-Headers: accept, authorization, content-type
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Date: Wed, 04 Nov 2020 09:25:20 GMT
Content-Length: 173
However, in Power Automate the Authorization header is suppressed, the HTTP action gives only the following headers: -
Pragma no-cache
Vary Accept-Encoding
Access-Control-Allow-Origin *
Access-Control-Allow-Headers Origin, X-Requested-With, Content-Type, Accept, Authorization
Access-Control-Expose-Headers accept, authorization, content-type
X-Frame-Options SAMEORIGIN
X-XSS-Protection 1; mode=block
Cache-Control no-store, no-cache
Date Wed, 04 Nov 2020 08:04:23 GMT
X-Powered-By ASP.NET
Content-Type text/html
Expires -1
Content-Length 60
Although I can't find any documentation for the HTTP action (am I missing something?) it seems to be that these headers are suppressed for security reasons. The same is also true if I create a Custom Connector.
Is there a way of turning this suppression off so that I can get to the header content that I need?
Thanks in advance
Kind Regards
Jonathan
