I’m trying to start a textract job using a http node. I have set up the aws credentials, and they do have permissions. I use the aws credential succesfully for example for the standard s3 and dynamodb node, but on the http node with predefined credentials type it does not work. I get the error of missing authorization token.
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Have you tried accessing the API via any other HTTP client like Postman or curl, for example? Does it work that way?
Hey @Radu , perhaps you are using the credentials not valid for this connection. You mention the authorization header. That might imply the Header Auth instead of what you use.
When using Header Auth, the header will be added to the HTTP request, though not reflected in the UI. You can also see what is actually sent out with the request in the Developers Console.
For example, here I applied Header Auth. They are not in UI but the Console shows they were added to the request.
the aws dynamodb node, has a custom call where it recommends to use it with predefined credentials. This is my problem, even if i try for dynamo a http call i get the same error
@Radu , what happens if you use a dedicated AWS Textract node. Do predefined credentials work in that way? If so, than your HTTP Request node configuration is missing something. You need to check the AWS documentation how to set it up the right way.
@ihortom yes they work properly on any dedicated AWS node. The problem is that according to the n8n official docs, you can choose predefined credentials as authorization as my link above, and that specific part does not work. The predefined credentials for authorization don’t add any headers for authorization as advertised in the documentation.
this is obviously a but, as the predefined credentials should add the authorization headers. Why it that field there if it doesn’t add the credentials? It does not make sense to have it and no doing anything, so obviously a bug …
unfortunatly for me I don’t think I’m gonna keep the subscription on the cloud version, and will search for alternatives … or default to coding
