{"type":"http.ClientResponse","code":403,"headers":{"Content-Length":"176","content-length":"176","Content-Type":"application/json","content-type":"application/json","Date":"Tue, 29 Apr 2025 201230 GMT","date":"Tue, 29 Apr 2025 201230 GMT","Via":"1.1 mono001","via":"1.1 mono001","x-amz-apigw-id":"JzTbWGY-DoEERbw=","X-Amz-Apigw-Id":"JzTbWGY-DoEERbw=","x-amzn-ErrorType":"IncompleteSignatureException","x-amzn-errortype":"IncompleteSignatureException","X-Amzn-Errortype":"IncompleteSignatureException","x-amzn-RequestId":"f3d7bf43-e105-44dc-b17e-b37eceb7ce92","x-amzn-requestid":"f3d7bf43-e105-44dc-b17e-b37eceb7ce92","X-Amzn-Requestid":"f3d7bf43-e105-44dc-b17e-b37eceb7ce92"},"body":"{\"message\":\"Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'xhthwN7LYmDD1RTzMb6KAS1inDnFxjBwbtdvubkSRz0='.\"}"}

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue is related to the authorization process when making requests to the REST API. The error message

InvalidSignature

indicates that the signature used in the authorization header is not valid. This could be due to a number of reasons such as incorrect encoding of the parameters in the authorization header, incorrect values being used in the signature, or the signature not being escaped properly. In the first thread, the user is getting a 403 error when making a request from a third party. The error message suggests that there is an issue with the signature in the authorization header. The user is advised to check the request in the login audit trial record and compare the signature with the one calculated by themselves. In the second thread, the user is having an issue with the

authValue

in their request. They found out that they had the request URL in the secret field instead of the token secret, which was causing the issue. In the third thread, the user is getting intermittent 401 Unauthorized errors when using the REST API. The audit log shows

InvalidSignature

as the error. The user is advised to ensure they are encoding the parameters in the authorization header and to consider using a library like RestSharp to handle the authorization. In all cases, it's important to ensure that the signature used in the authorization header is correctly generated and encoded. This includes making sure that all parameters are correctly included and that any special characters are properly escaped.