nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Get Region Name

Duarte Oliveira

Hello All,

I'm trying to get the attribute region name (attr_#_#) from the category and attribute name but i don't find the any function.

There any Webservice to this ?

Thanks.

Duarte

Find more posts tagged with

Comments

Kyle_Swidrovich

I’d recommend using the Search API for that:

https://knowledge.opentext.com/knowledge/cs.dll/Open/16579994

Specifically, you’d be interested in the search.getCategory call.

Regards,

Kyle

Duarte Oliveira

Hello Kelly,

The method getCategory doesn't exist on Search Service (Web Services SDK) and the method Document Mamager.GetCategoryDefinition doesn't return the attribute region name (<attr_#_#>)

Thanks.

Duarte Oliveira

Kelly=Kyle. Sorry

Appu_Nair1

Kyle probably meant this API

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

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Monday, March 11, 2013 11:48 AM
To: eLink Recipient
Subject: [EXTERNAL]RE Get Region Name

RE Get Region Name

Posted by doliveira@glintt.com (Oliveira, Duarte) On 03-11-2013 12:29

Kelly=Kyle. Sorry

[To post a comment, use the normal reply function]
Topic:	Get Region Name
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Duarte Oliveira

You posted the same URL as Kyle.

The API is different when using WebServices SDK.

Quoted Appu Nair on 2013-03-11 18:22:

Kyle probably meant this API

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

RE Get Region Name

Posted by doliveira@glintt.com (Oliveira, Duarte) On 03-11-2013 12:29

Kelly=Kyle. Sorry

[To post a comment, use the normal reply function]
Topic:	Get Region Name
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Kyle_Swidrovich

That is correct.

We strongly recommend using the Search API that I linked to as opposed to the web services offering.

All dev efforts are going into that Search API and no further features are being added to the SearchService web services API.

Duarte Oliveira

OpenText advise the use of search API instead of WebServices ? WebServices is a standard for integration between heterogeneous systems.

Search API is suitable for external aplications to archive and retreive objects from Content Server (i don't find any authentication function on search api) ?

We start our development based on web services SDK and it's very critical now to change all code to search api. So there anyway to get the region name via WS ?

thanks

Quoted Kyle Swidrovich on 2013-03-11 22:36:

That is correct.

We strongly recommend using the Search API that I linked to as opposed to the web services offering.

All dev efforts are going into that Search API and no further features are being added to the SearchService web services API.

Vanderpoel_Rob

Hi Duarte,

The code below is my brute force approach. I don't know how reliable it is because it hasn't received a lot of testing but see how you go.

Sorry, lost the indenting on the cut-and-paste.

Cheers

Rob

private static string GetAttributeRegionId(DocumentManagement. DocumentManagementClient dc, ref DocumentManagement. OTAuthentication dmOTAuth, string CategoryName, string AttributeName)

{

// Obtain the region id (e.g. attr_123345_6) for category and attribute. Required for searches

string retVal = "" ;

DocumentManagement. Node [] categories = dc.ListNodes( ref dmOTAuth, 2004, true );

for ( int i = 0; i < (categories.Length); i++)

{

DocumentManagement. Node category = categories[i];

//Console.WriteLine(category.Name);

if (category.Name.ToUpper() == CategoryName.ToUpper())

{

DocumentManagement. AttributeGroupDefinition attributes = dc.GetCategoryDefinition( ref dmOTAuth, category.ID);

foreach (DocumentManagement. Attribute attribute in attributes.Attributes)

{

//Console.WriteLine(attribute.DisplayName + ", " + attribute.ID + ", " + attribute.Key + ", " + attribute.Type);

//Console.WriteLine(" region id: Attr_" + category.ID + "_" + attribute.ID);

if (attribute.DisplayName.ToUpper() == AttributeName.ToUpper())

{

//Console.WriteLine(" Found Attr_" + category.ID + "_" + attribute.ID);

retVal = "Attr_" + category.ID + "_" + attribute.ID;

}

return retVal;

}

Kyle_Swidrovich

Hi Duarte,

The features of the SearchService API are still supported, however, no new features will be added to the SearchService to extend what’s already shipping.

I was suggesting that any new development should use the Search API if you’d like to take advantage of any new features being added to product (e.g., the getCategory function).

The SearchService web service, as you have probably noticed, is not easy to use.

Parsing the response correctly without having an example, such as the one I posted, is difficult to do.

Customers and partners have noted that the Search API is easier to comprehend and provides a much richer set of features.

If you’re already using the Web Services APIs, that’s fine. However, you will be unable to take advantage of some of these other features only available to the Search API without calling it separately.

Rob’s example posted here is a good approximation to how the region names are generated (Attr_CATID_ATTRID), however, it should probably be extended to only return region names for attributes marked as “Show in Search”.

Attributes with that checkbox disabled are not searchable.

Regards,

Kyle

Duarte Oliveira

Hi Rob,

You code is fine for my needs.

Thanks a lot.

Quoted Rob Vanderpoel on 2013-03-12 09:55:

Hi Duarte,

The code below is my brute force approach. I don't know how reliable it is because it hasn't received a lot of testing but see how you go.

Sorry, lost the indenting on the cut-and-paste.

Cheers

Rob

private static string GetAttributeRegionId(DocumentManagement. DocumentManagementClient dc, ref DocumentManagement. OTAuthentication dmOTAuth, string CategoryName, string AttributeName)

{

// Obtain the region id (e.g. attr_123345_6) for category and attribute. Required for searches

string retVal = "" ;

DocumentManagement. Node [] categories = dc.ListNodes( ref dmOTAuth, 2004, true );

for ( int i = 0; i < (categories.Length); i++)

{

DocumentManagement. Node category = categories[i];

//Console.WriteLine(category.Name);

if (category.Name.ToUpper() == CategoryName.ToUpper())

{

DocumentManagement. AttributeGroupDefinition attributes = dc.GetCategoryDefinition( ref dmOTAuth, category.ID);

foreach (DocumentManagement. Attribute attribute in attributes.Attributes)

{

//Console.WriteLine(attribute.DisplayName + ", " + attribute.ID + ", " + attribute.Key + ", " + attribute.Type);

//Console.WriteLine(" region id: Attr_" + category.ID + "_" + attribute.ID);

if (attribute.DisplayName.ToUpper() == AttributeName.ToUpper())

{

//Console.WriteLine(" Found Attr_" + category.ID + "_" + attribute.ID);

retVal = "Attr_" + category.ID + "_" + attribute.ID;

}

return retVal;

}

Duarte Oliveira

Kyle,

I just don't understand how to pass the authentication with the search API. I didn't find information on API documentation.

Can you give me some sample how to access to search API from an external application ?

Thanks.

Duarte

Kyle_Swidrovich

If you’re using standard Content Server authentication in the web service, the authentication token you get back from AuthenticateUser can be used as the value for the “LLCookie” cookie.

This cookie, when passed in with a Search API request, will allow you to pass in an authenticated request.

Duarte Oliveira

Hello Kyle

I'm trying to connect from a remote sever to ontent server but when i treid to get the category list xml (func=ll&ObjID=2004&objAction=XMLExport&scope=1) i get this error:

"Your request originated from a website that Content Server identified as potentially unsafe."

I'm passing the LLCookie with authentication token but doesn't work.

This is the c# code i'm using:

AuthenticationClient authClient = new AuthenticationClient();

string authToken = null;

authToken = authClient.AuthenticateUser("admin", "livelink");

CookieContainer cookie = new CookieContainer();

cookie.Add(new Uri("http://10.250.46.62"), new Cookie("LLCookie", authToken));

HttpWebRequest request = (HttpWebRequest)WebRequest.Create("http://10.250.46.62/OTCS/llisapi.dll?func=ll&ObjID=2004&objAction=XMLExport&scope=1");

request.CookieContainer = cookie;

request.Method = "POST";

request.ContentType = "text/html";

request.ContentLength = 0;

HttpWebResponse WebResp = (HttpWebResponse)request.GetResponse();

Console.WriteLine(WebResp.StatusCode);

Console.WriteLine(WebResp.Server);

Stream Answer = WebResp.GetResponseStream();

StreamReader _Answer = new StreamReader(Answer);

Category = "Resposta (token - " + authToken + ": *" + _Answer.ReadToEnd() + "*";

Can you help me ?

Thanks.

Quoted Kyle Swidrovich on 2013-03-19 18:03:

If you’re using standard Content Server authentication in the web service, the authentication token you get back from AuthenticateUser can be used as the value for the “LLCookie” cookie.

This cookie, when passed in with a Search API request, will allow you to pass in an authenticated request.

sıɹɥɔ

Quoted Duarte Oliveira on 2013-03-19 11:49:

"Your request originated from a website that Content Server identified as potentially unsafe."

I'm passing the LLCookie with authentication token but doesn't work.

That message is the result of a security mechanism. See https://knowledge.opentext.com/knowledge/cs.dll/Open/14582189 for details.

To resolve your issue you'll want to include a referer header in your request that satisfies the system's security configuration.

Hope this helps,

-chris

Appu_Nair1

Kyle/Jason

Could you enlighten me why putting the Authentication Token in a piece of C#/.NEt/java code to call the searchAPI

apparently to stop livelink asking for creds is a good idea? The idea of setting a cookie to livelink's URL header

is in my mind akin to hardcoding a userid/password in the request URL first to get a cookie

something like this is what I had in mind.The nextURL would take me to the searchApi

http://llappu971vm:8080/livelink/livelink.exe?func=ll.login&username=livelinkuser&password=livelinkpassword&nextURL=/livelink/livelink.exe?func=ll&objId=670175&objAction=browse&viewType=1

if HTTPS was not active in my livelink webserver involved would not the first authentication call to livelink's webservice to get a token be sending the

userid/password in clear text.I am just not understanding why putting the cookie returned from the webservice

into a livelink URL is in a way safer than justs ending the login creds in the URL.

Carsten_Kulms

One issue with credentials or other authentication data in URL is that a request URL is usually logged in the web server's access log.Of course this must not be the case and there may be environments where even HTTP headers (like cookie) are logged nonetheless it should be avoided to pass sensitive data in URL.Another issue is that the cookie is valid for a limited time only if running CS with reasonable or the default security settings.Also it can be bound to the client's IP address (or parts of it; again a default setting). So even if one masters to capture a particular cookie instance from a request there is a good chance that he cannot benefit from that.In contrast, username/password credentials usually don't change frequently and are not secured by any other means neither.In the scenario discussed in this thread the cookie is already available so why not using it?Furthermore this way the application does not need to store the user's password after initial authentication. And in case other than username/password authentication is set up than this will still work.(The non-httpS case doesn't really need discussion, I think, as it is inherently insecure.)