REST WebService - Random Unauthorized Error (HTTP 401)

Hi,

I'm trying out REST Webservices with CS 16.2.3 and I encountered a 401 unauthorized error even though I have a valid otcs ticket generated.

The strangest thing is this error happens randomly. Some REST call will throw out 401 error while some will successfully display the json result. I've realise that this could be due to the otcs ticket generated. I'm using the same otcs ticket for 2-3 rest methods. If the first method executes successfully, the subsequent methods will follow suit. However, if the first method threw a 401 unauthorized error, the subsequesnt methods will throw the same error as well.

I have already encoded the ticket with UTF-8 before sending a request so I not too sure what could be the issue. Any advice would be much appreciated.

Find more posts tagged with

Comments

Hans Stoop

I don’t remember the details, but it goes wrong when the ticket contains a certain character. I think it was & but maybe a / or something else. It should or shouldn’t be encoded.

Hans

On 11. Apr 2018, at 05:19, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : REST WebService - Random Unauthorized Error (HTTP 401)
REST WebService - Random Unauthorized Error (HTTP 401) Posted by shemin.ang@atos.net (Ang, Shemin) On 04/10/2018 11:15 PM

Hi,I'm trying out REST Webservices with CS 16.2.3 and I encountered a 401 unauthorized error even though I have a valid otcs ticket generated.The strangest thing is this error happens randomly. Some REST call will throw out 401 error while some will successfully display the json result. I've realise that this could be due to the otcs ticket generated. I'm using the same otcs ticket for 2-3 rest methods. If the first method executes successfully, the subsequent methods will follow suit. However, if the first method threw a 401 unauthorized error, the subsequesnt methods will throw the same error as well.I have already encoded the ticket with UTF-8 before sending a request so I not too sure what could be the issue. Any advice would be much appreciated.
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: My Support

Shemin_Ang

Thks Han!

Yes, you are right. I remove the encoding for the ticket and it works now.

Ferdinand Prantl

The CS REST API authentication ticket obtained by "POST /auth" contains only printable characters from lower ASCII. No need to decode it. No need to encode it, when setting it to the OTCSTicket request header.