Newly Configured REST Server resource fails with 400 or “It is not on the appropriate screen or unknown” error

View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere MFT. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
1 post Page 1 of 1

Support_Jerrod

Support Specialist
Posts: 11
Joined: Wed Dec 13, 2017 5:52 pm

Post by Support_Jerrod » Fri Jul 05, 2019 4:48 pm
In some older versions of REST server implementations, authentication is transmitted preemptively opposed to when a client connects to the server, and the server asks the client to login. In this scenario, the REST server requires authentication to occur in a request header upon connection.

In order to fulfil this requirement, a Request Header element can be added to the REST (post, Get, Put, etc.) command task. The Name value should be Authorization with a Value of Basic (base 64 encoded string for username:password) PLEASE NOTE, this does not include the brackets from the following image, it should be "Basic string value" where string value represents the base 64 encoded string of username:password.
restauth.jpg
Jerrod Foster
Support Analyst

e. [email protected]
p. 1.800.949.4696
w. HelpSystems.com
1 post Page 1 of 1