Contributions
Not Authorized message when submitting POST request
Submitting POST JSON request via Postman works perfectly. Imported the Postman collection to ReadyAPI but when executing the request, I'm receiving a Not Authorized message. Sample JSON below. Seems to be ignoring the auth section. Any ideas? POST {service.endpoint}/clients/api HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json Content-Length: 2524 Host: {service.endpoint} Connection: Keep-Alive User-Agent: Apache-HttpClient/4.5.2 (Java/15) { "auth" : { "user_id" : "19644", "api_key" : "dbf067d8609igiot8i6troiuvoiuyfuyfg43ea702d" }, "order" : { "type" : "New", "client_file_number" : "123456789A", "lender" : "Some Bank", "loan_amount" : "200000", "loan_number" : "1234-5678-90", "full_street_address" : "123 Main St.", "street_number" : "123", "street_name" : "Main St." }3 years agoPlace ReadyAPI QuestionsReadyAPI Questions672Views0likes2CommentsRe: Missing header
I manually add the header and it appears in the Raw Request, however, I still get the message. As noted in my original inquiry, this works fine in Postman and worked previously in Ready API. It broke when the service was moved to AZURE. I suspect that some security function is stripping out the header, but was looking to see if anyone else has experienced any issues after the services moved to the cloud. POST https://cplxxxxuture.abc.com/v3/ABCManagement.svc HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: text/xml;charset=UTF-8 SOAPAction: "GetABCMetaData" Authorization: Bearer eyJhbGciOiJSUzI1UrkpgYaXznJhPNPCEfbnsLJiJYwg ClientID: A42F5 Content-Length: 937 Host: cpltrainfuture.fnf.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.5.2 (Java/12.0.1)4 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.6KViews0likes0CommentsMissing header
When submitting a request with an Authorization header, it seems to be stripped out when it is received. Message returned is "Bad Request: The authorization header is null or empty or isn't bearer. Please contact support." Developers verify that the header is missing, not that the token is null or empty. Request works fine in Postman, just not Ready API. This broke when the service was moved to Azure.Solved4 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.8KViews0likes3Comments