Rest API CS16 doesn't seem to be working the same way as in CS10

Hi All,

We've been using Rest API's for Content Server Search for a few years now. We are about to upgrade to CS16, and I am having a hard time making the SAME code work! Since it could be our setup or feature(s) not available in CS16, I will show the browser query which WORKS from the browser:

http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml

where <hostname> is our internal server name, and <rootNodId> is the search root.

Again, this exact query works in CS10 and ALSO works in the browser in CS16.

The SAME query works fine when sent from .Net code in CS10, but fails when sent in CS16 environment.

Here is code sample I am using to send the query, unchanged between CS10 and CS16:

using System;

using System.Diagnostics;

using System.IO;

using System.Net.Http;

using System.Net.Http.Headers;

using System.Text;

namespace ConsoleApplicationWCF{

 class Program

{

private const string un = "username", // our username

pw = "password", // our password

queryCommand = "http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml";

static void Main(string[] args)

{

HttpResponseMessage result = null;

using (var client = new HttpClient(new HttpClientHandler() { UseDefaultCredentials = true }))

{

client.BaseAddress = new Uri(queryCommand);

string authentication = Convert.ToBase64String(Encoding.UTF8.GetBytes(un + ":" + pw));

client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", authentication);

client.GetAsync(queryCommand).ContinueWith(z => result = z.Result).Wait();

}

string response = String.Empty;

using (Stream receiveStream = result.Content.ReadAsStreamAsync().Result)

{

using (StreamReader readStream = new StreamReader(receiveStream))

{

response = readStream.ReadToEnd();

}

Console.WriteLine(response);

Trace.WriteLine(response);

Console.ReadKey();

}

When I run this on CS16 I get some malformed pages in response:

<!DOCTYPE html>

<html>

<p><strong>Note:</strong>Since your browser does not support Javascript, you must press the Continue button once to proceed.</p>

</noscript>

<form action="https://<hostname>/otcs/llisapi.dll" method="post">

<div>

<input type="hidden" name="redirectURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/>

<input type="hidden" name="NextURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/>

</div>

</noscript>

</form>

</body>

</html>

Any help would be much appreciated!

Thanks!

Find more posts tagged with

Comments

eLink User

Have you seen this OT article by a helpful KB OT Poster

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=61395475&objAction=ArticleView&viewType=1

I think you are getting not past the OTDS token.If that does not work you can configure a livelink server to not use OTDS forward service.

OTDS if you are new is a "man in the middle" implementation.You ask Livelink for doing something.If OTDS is doing the auth it will redirect to the

OTDS server(A tomcat) then it will check your authentication call ,if you pass that then it will stuff a header(token),this token is parsed by the

livelink appserver and it will use that for your login.

A convenient webservices function was recently introduced that says take the OTDS token and make it the auth token of livelink

.I also think your code might work straight with IWA if it is windows,i Have no working OTDS at this time to check,but apparently

if you put fiddler you should see your first hit to the livelink server go to the OTDS server and back,that is probably what your code

is getting and probably code cannot re-direct like a browser does.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Aug 16, 2016 at 2:21 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Rest API CS16 doesn't seem to be working the same way as in CS10 Posted byFilman, EugeneOn 08/16/2016 03:19 PM

Hi All,We've been using Rest API's for Content Server Search for a few years now. We are about to upgrade to CS16, and I am having a hard time making the SAME code work! Since it could be our setup or feature(s) not available in CS16, I will show the browser query which WORKS from the browser:http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xmlwhere <hostname> is our internal server name, and <rootNodId> is the search root.Again, this exact query works in CS10 and ALSO works in the browser in CS16.The SAME query works fine when sent from .Net code in CS10, but fails when sent in CS16 environment.Here is code sample I am using to send the query, unchanged between CS10 and CS16:using System;using System.Diagnostics;using System.IO;using System.Net.Http;using System.Net.Http.Headers;using System.Text;namespace ConsoleApplicationWCF{ class Program{ private const string un = "username", // our username pw = "password", // our password queryCommand = "http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"; static void Main(string[] args) { HttpResponseMessage result = null; using (var client = new HttpClient(new HttpClientHandler() { UseDefaultCredentials = true })) { client.BaseAddress = new Uri(queryCommand); string authentication = Convert.ToBase64String(Encoding.UTF8.GetBytes(un + ":" + pw)); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", authentication); client.GetAsync(queryCommand).ContinueWith(z => result = z.Result).Wait(); } string response = String.Empty; using (Stream receiveStream = result.Content.ReadAsStreamAsync().Result) { using (StreamReader readStream = new StreamReader(receiveStream)) { response = readStream.ReadToEnd(); } } Console.WriteLine(response); Trace.WriteLine(response); Console.ReadKey(); }}}When I run this on CS16 I get some malformed pages in response:<!DOCTYPE html><html> <body onload="document.forms[0].submit()"> <noscript> <p><strong>Note:</strong>Since your browser does not support Javascript, you must press the Continue button once to proceed.</p> </noscript> <form action="https://<hostname>/otcs/llisapi.dll" method="post"> <div> <input type="hidden" name="OTDSTicket" value="*VER2*ABS3wOCSR4O40Uc3UJLleH8_0CblXQAQHPrRX18ZxisUrWclHvQFKgKwnLM-kDn5rptB7Is2F-GUVCXz3FQKsxeWhGIC7EMTT1rGG41TsHKb0QWpSyaXcZoBa86BwA2VL3iRm1QsHXrzRPARnUbXvMqJwkdWBSrOTbaJEUusepsLdSd0kX1MxPpqSTBCy7Bv54PCtdz9zZf9xFiAhTTIei1nWODvduHOL8MRHxhJKKs3I9ioR0fpnHTib85Jt6yKJQUSZxDyJ-HC_E1XDCZL-XJ1YEcSSeDsF8G-0IUoiujN9Xw5HDpfjl2ulF3JC46WG4TQW-FE8kiInCAqG_bkdYQlkbEfE-eeJtZ8O2wryywH2Tre4fmTs9l3nDwUxpDFavvyyRhFcIz_gItat9bjouKgWwKbUthS7nXQiCWaB5toV5k1a96xexhBsknWzePnOsp6KE8t2qiNwuE_Fyf7wc7hPvJ9c4eA-XamGU-EynFCPZQb14XoVdizlBb-__wRRYpu6dOrJlC8tR0Yg_Hz35C2sX4RS93wmCi3GYjRhfz7oeTk-C0O4qqFRqD-YFeLkxQr9ybSbuVm0q_XKUxmz7luVgL3O7M2l3R3bGZixojxurQgbbMxT8MYGA-x4QU3N-yaYG-zISuT-oZeEzWNPm8POEYrCHxkrVA9a26NQ0jv3A9x_dmoAEleH5SHkCid7oNK_HEtnoiJETbDhqaZVV4zBOShtgXtSBopcBYZyQHcYdJhW6lLNU2ZfjLg7pcGxHo60PhOCoO_ufkhO8MMbSQDWwaRIBTLRm0y9ARfEj709jvD8zGA0j8oHapw7VW6jayEOfmoT60O_UjpmG2C2dngCYr_i7-TtUB9y7fVPuXf1KDJLMXhiu1lrtOKQw5pjB1VOV4DlnvMhsULHh6EMrOj6bx7Fays8dlzzgaa5NRqLFMWbV6XhkD6ypaamcytq9-vIZt34lWEkQ**"/> <input type="hidden" name="redirectURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/> <input type="hidden" name="func" value="otdsintegration.redirect"/> <input type="hidden" name="NextURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/> </div> <noscript> <div><input type="submit" value="Continue"></div> </noscript> </form> </body></html> Any help would be much appreciated!Thanks!
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

eLink User

Have you seen this OT article by a helpful KB OT Poster

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=61395475&objAction=ArticleView&viewType=1

I think you are getting not past the OTDS token.If that does not work you can configure a livelink server to not use OTDS forward service.

OTDS if you are new is a "man in the middle" implementation.You ask Livelink for doing something.If OTDS is doing the auth it will redirect to the

OTDS server(A tomcat) then it will check your authentication call ,if you pass that then it will stuff a header(token),this token is parsed by the

livelink appserver and it will use that for your login.

A convenient webservices function was recently introduced that says take the OTDS token and make it the auth token of livelink

.I also think your code might work straight with IWA if it is windows,i Have no working OTDS at this time to check,but apparently

if you put fiddler you should see your first hit to the livelink server go to the OTDS server and back,that is probably what your code

is getting and probably code cannot re-direct like a browser does.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Aug 16, 2016 at 2:21 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Rest API CS16 doesn't seem to be working the same way as in CS10 Posted byFilman, EugeneOn 08/16/2016 03:19 PM

Hi All,We've been using Rest API's for Content Server Search for a few years now. We are about to upgrade to CS16, and I am having a hard time making the SAME code work! Since it could be our setup or feature(s) not available in CS16, I will show the browser query which WORKS from the browser:http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xmlwhere <hostname> is our internal server name, and <rootNodId> is the search root.Again, this exact query works in CS10 and ALSO works in the browser in CS16.The SAME query works fine when sent from .Net code in CS10, but fails when sent in CS16 environment.Here is code sample I am using to send the query, unchanged between CS10 and CS16:using System;using System.Diagnostics;using System.IO;using System.Net.Http;using System.Net.Http.Headers;using System.Text;namespace ConsoleApplicationWCF{ class Program{ private const string un = "username", // our username pw = "password", // our password queryCommand = "http://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"; static void Main(string[] args) { HttpResponseMessage result = null; using (var client = new HttpClient(new HttpClientHandler() { UseDefaultCredentials = true })) { client.BaseAddress = new Uri(queryCommand); string authentication = Convert.ToBase64String(Encoding.UTF8.GetBytes(un + ":" + pw)); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", authentication); client.GetAsync(queryCommand).ContinueWith(z => result = z.Result).Wait(); } string response = String.Empty; using (Stream receiveStream = result.Content.ReadAsStreamAsync().Result) { using (StreamReader readStream = new StreamReader(receiveStream)) { response = readStream.ReadToEnd(); } } Console.WriteLine(response); Trace.WriteLine(response); Console.ReadKey(); }}}When I run this on CS16 I get some malformed pages in response:<!DOCTYPE html><html> <body onload="document.forms[0].submit()"> <noscript> <p><strong>Note:</strong>Since your browser does not support Javascript, you must press the Continue button once to proceed.</p> </noscript> <form action="https://<hostname>/otcs/llisapi.dll" method="post"> <div> <input type="hidden" name="OTDSTicket" value="*VER2*ABS3wOCSR4O40Uc3UJLleH8_0CblXQAQHPrRX18ZxisUrWclHvQFKgKwnLM-kDn5rptB7Is2F-GUVCXz3FQKsxeWhGIC7EMTT1rGG41TsHKb0QWpSyaXcZoBa86BwA2VL3iRm1QsHXrzRPARnUbXvMqJwkdWBSrOTbaJEUusepsLdSd0kX1MxPpqSTBCy7Bv54PCtdz9zZf9xFiAhTTIei1nWODvduHOL8MRHxhJKKs3I9ioR0fpnHTib85Jt6yKJQUSZxDyJ-HC_E1XDCZL-XJ1YEcSSeDsF8G-0IUoiujN9Xw5HDpfjl2ulF3JC46WG4TQW-FE8kiInCAqG_bkdYQlkbEfE-eeJtZ8O2wryywH2Tre4fmTs9l3nDwUxpDFavvyyRhFcIz_gItat9bjouKgWwKbUthS7nXQiCWaB5toV5k1a96xexhBsknWzePnOsp6KE8t2qiNwuE_Fyf7wc7hPvJ9c4eA-XamGU-EynFCPZQb14XoVdizlBb-__wRRYpu6dOrJlC8tR0Yg_Hz35C2sX4RS93wmCi3GYjRhfz7oeTk-C0O4qqFRqD-YFeLkxQr9ybSbuVm0q_XKUxmz7luVgL3O7M2l3R3bGZixojxurQgbbMxT8MYGA-x4QU3N-yaYG-zISuT-oZeEzWNPm8POEYrCHxkrVA9a26NQ0jv3A9x_dmoAEleH5SHkCid7oNK_HEtnoiJETbDhqaZVV4zBOShtgXtSBopcBYZyQHcYdJhW6lLNU2ZfjLg7pcGxHo60PhOCoO_ufkhO8MMbSQDWwaRIBTLRm0y9ARfEj709jvD8zGA0j8oHapw7VW6jayEOfmoT60O_UjpmG2C2dngCYr_i7-TtUB9y7fVPuXf1KDJLMXhiu1lrtOKQw5pjB1VOV4DlnvMhsULHh6EMrOj6bx7Fays8dlzzgaa5NRqLFMWbV6XhkD6ypaamcytq9-vIZt34lWEkQ**"/> <input type="hidden" name="redirectURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/> <input type="hidden" name="func" value="otdsintegration.redirect"/> <input type="hidden" name="NextURL" value="https://<hostname>/otcs/llisapi.dll?func=search&dspRegion1=OTDataID&dspRegion2=OTName&dspRegion3=OTDataSize&boolean1=and&lookFor1=complexquery&where1=OTLocation:<rootNodeId>&outputformat=xml"/> </div> <noscript> <div><input type="submit" value="Continue"></div> </noscript> </form> </body></html> Any help would be much appreciated!Thanks!
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

Eugene_Filman

Thank you for your reply. Can you point to an example of how to create this token and pass it along? The reason I am asking because I already create an authentication header with basic authentication (see above), and pass it along. So, if there is a special way to create the "token", I can certainly try that. Thanks!

eLink User

I thought the OpenText article was giving you that.The function the poster has REST_Authenticate includes and userid/password in clear text.If not try developer.opentext.com there are plenty of RESTAPI code there.You may also find lots of examples in the OT KB from where I posted the KB article.There is more than one example detailing how to use XML Search API with these modern authentication methods .

In the CWS forum this Link https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=62345549&objAction=browse&viewType=1

and this https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=62345549&objAction=browse&viewType=1

has examples on how to authenticate using the OTDS server

Hopefully you can find something useful in these publications.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Wed, Aug 17, 2016 at 9:53 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re Rest API CS16 doesn't seem to be working the same way as in CS10 2 Posted byFilman, EugeneOn 08/17/2016 10:50 AM

Thank you for your reply. Can you point to an example of how to create this token and pass it along? The reason I am asking because I already create an authentication header with basic authentication (see above), and pass it along. So, if there is a special way to create the "token", I can certainly try that. Thanks!
[To post a comment, use the normal reply function]
Topic: Rest API CS16 doesn't seem to be working the same way as in CS10
Forum: Content Web Services Forum
Content Server: Knowledge Center

Eugene_Filman

Sorry, both links are taking me to an empty page with one Test folder, with no files in it.

eLink User

The links are to the forum documentation examples as such.All of the graphics(Pictures) you see are hyperlinks

As you said somebody at OT has created a TEST folder in here do not know its purpose but i would try clicking on one of these

huge GRAPHICs You must be knew to the ways of the KB.

Attached also article I indicated in my very first post.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Wed, Aug 17, 2016 at 12:36 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re Re Rest API CS16 doesn't seem to be working the same way as in CS10 2 Posted byFilman, EugeneOn 08/17/2016 01:30 PM

Sorry, both links are taking me to an empty page with one Test folder, with no files in it.
[To post a comment, use the normal reply function]Topic:Rest API CS16 doesn't seem to be working the same way as in CS10Forum:Content Web Services ForumContent Server:Knowledge Center

image.png

Content Server - Web Services - How to use Search API with REST authentication .docx

eLink User

The links are to the forum documentation examples as such.All of the graphics(Pictures) you see are hyperlinks

As you said somebody at OT has created a TEST folder in here do not know its purpose but i would try clicking on one of these

huge GRAPHICs You must be knew to the ways of the KB.

Attached also article I indicated in my very first post.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Wed, Aug 17, 2016 at 12:36 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re Re Rest API CS16 doesn't seem to be working the same way as in CS10 2 Posted byFilman, EugeneOn 08/17/2016 01:30 PM

Sorry, both links are taking me to an empty page with one Test folder, with no files in it.
[To post a comment, use the normal reply function]Topic:Rest API CS16 doesn't seem to be working the same way as in CS10Forum:Content Web Services ForumContent Server:Knowledge Center

image.png

Content Server - Web Services - How to use Search API with REST authentication .docx

André_Roy

Here you will find documentation (API reference) and examples (Getting Started With C#/Java) for CWS.
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=45500683&objAction=browse&viewType=1

For example, under the ‘Getting Started’ link, there is another link for ‘OTDS Authentication’. It has a code example with screenshots.

Regards,

André Roy
Principal Technical Analyst

Eugene_Filman

Thank you both for you replies. I have done some CS development, no worries :-) Before asking, I looked at C# code at legnth, it's pretty basic, and uses WCF everywhere, there are NO REST API examples.

Andre, my specific question was regarding REST API, we have an existing code base, which we don't want to change at this point in time. While doing CS16 upgrade, we are unable to use Search REST API's, that's what started this thread.

André_Roy

Hi Eugene,

Yes, but I thought you were looking for an example to get a token/cookie via CWS, then pass it to OTDS?

Have you seen this forum post?
https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=61382047&objAction=viewincontainer

Looks like Peter Varga provided a great response for the same or similar issue.

Regards,

André Roy
Principal Technical Analyst

AKropp

Hi Eugene,

Attached is code I use to obtain and parse a REST auth ticket from the CS REST API. It works just fine with the Search XML API. Appu posted a link to another sample a colleague of mine wrote that uses C# builtins to deserialize the token which I felt to be a bit overly complex. Mine uses the FOSS Json.net libraries (available from Newtonsoft’s site or through the Nuget manager in VS) which seemed much simpler to implement, at least to my eyes.

I’m no OTDS expert, but now that it’s mandatory I don’t think you can get away with just doing this basic auth header (just search developer.opentext.com for “SSO” to see all the lively discussions). CS wants a ticket from somewhere “authoritative”, and there’s a lot of ways to get one (CWS, CS REST API, llcookie), so I guess it’s a matter of picking the one that works best for you. If someone else out there knows another way I’d definitely like to add it to my toolkit!

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Wednesday, August 17, 2016 4:18 PM
To: eLink Recipient
Subject: Re Re Rest API CS16 doesn't seem to be working the same way as in CS10 2

Re Re Rest API CS16 doesn't seem to be working the same way as in CS10 2

Posted by Filman, Eugene On 08/17/2016 04:15 PM

[To post a comment, use the normal reply function]
Topic:	Rest API CS16 doesn't seem to be working the same way as in CS10
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

rest auth.txt

Eugene_Filman

Thank you, this is a really good example. But, as before, I am getting back the "The remote server returned an error: (401) Unauthorized." error. Any idea what settings should be changed on the server, to allow the authorizaiton? Thanks!

jdonpaul

Alex and Andres are correct. You will still need to authenticate first before attempting to use REST in an SSO styled application. there are multiple methods to do this, but the idea is still the same. In this case, you can use either the authentication web service to authenticate using SSO as per Peter Varga post and use the resulting token in your REST API calls. Another method is that you can make a simpe HTTP request to Content Server, and once signed in via SSO, you can extrapolate the token from the header files and use it with your REST API calls. My preference would be to make an authentication Web service call and then use the token from there to make my REST API calls.

Both the examples that Andre and Alex have provided should be sufficient to assist in building your application. What you will need to do is authenticate using Peter's example and then using the token from that, use Alex's example to complete your requests.

As for the HTTP 401 error, it means that you are unauthorized to access that URL resource. Most likely, it means that your web server is saying that you are not authenticated or that you have authenticated incorrectly. In general, the web server is sending back this response, not the web application.

JDP

Eugene_Filman

Thank you, I made quite a bit of progress - the "Not Authorized" issue seems to be with our setup, so we have our OpenText support working on it. Once they gave me a working user from a different partition, both REST Authentication and REST Search worked as expected.

One statement got me interested, since I was thinking the same way - to get the token using web services (WCF) and use it in REST API search. As I mentined, when token is received using REST Authenticaion, it works fine. However, when I get WCF token, and use it the same way (adding to search request headers), the search returns the same "Not Authorized" response.

I asked our support people, and they stated that authentication tokens are different, and I can't use WCF one for REST searches. Is this what you guys also think? Thanks,