Livelink Authentication

Hello all,

I have a requirement where through Web Services I have to display the heirarchy of folder structures in a tree view kind of a thing(like in the sample code), and then when the user traverses to a document and clicks on the document and new browser should open and display the document in it, without again asking for the authentication. This is the same thing which happens through livelink when we select any document and click on Open button, it displays the document in a browser. I have taken the URL from Livelink and generating the same URL through my java code, putting in the id and document name:

http://bg-bim-cs10/otcs/livelink.exe/17732/ECM Capability Model v5_dgw.pptx?func=doc.Fetch&nodeid=17732

The URL in Livelink and the one through my code comes like this. But the problem is that through my java code, it is prompting me for a login screen of Livelink. Can somebody suggest how can i directly open the document without asking for the credentials. Because the user is already logged in through the Java application, so he wont prefer to enter the password again and again.

Thanks.

Find more posts tagged with

Comments

Carsten_Kulms

If the goal is to show the user the document within you application then you should use the DocumentService to fetch the content.If your application is a web application (HTML UI) this could be done in a servlet - opened as a separate page - that streams the content to the client's browser (with proper content-type header).

Jason_Smith

When issuing the browser request you will need to set the LLCookie in the request for authentication. You get an LLCookie when you authenticate with CWS using the Authentication service’s AuthenticateUser() method.

Carsten_Kulms

Re-using the authentication token will be possible only if the CWS are deployed "standalone". In case they are deployed in RCS the token is not the same a LLCookie.(cf. also https://knowledge.opentext.com/knowledge/cs.dll/fetch/-15106263/15106294/15106295/16376487/17990637/17990649/17990650/18047148/clientguide.html?nodeid=18047748&vernum=-2#authentication)The method of fetching the content by means of DocumentManagement service - for rendering in your application or streaming it to the end-user's browser- will work in either case.If you attempt that your application spawns a separate browser window (or even process) with an URL the browser/HTML-based UI uses you will face several challenges even if the authentication token is a LLCookie; for example:- if your application (the web-service client) does not run on the end-user's machine also the cookie may not be usable at the end-user's machine due to the security settings- you need a way to pass the cookie to the browser instance in a way so that the cookie is transferred properly by the browser with the URL requestWhether any of this is possible at all depends on the nature of your application (web application, applet, fat client, ...) and probably implies some 'bads' from a security perspective in any case.(See also other the threads about similar stuff in this forum.)

Shruti_Mishra

This is the service which i am using to generate the token, com.opentext.livelink.service.core.Authentication.authenticateUser(String arg0, String arg1), but is the token generated will be same as LLCookie.

And if it is the same, can you suggest me how to set that cookie in the browser? I am just generating the URL and then hitting the URL. I am doing this through a Fat Client in .Net

I am very new to CWS, please help me with some examples,if possible.

Carsten_Kulms

This issue is not specific to CWS and there is no easy solution, I think.Maybe something like the following is feasible in your situation:http://stackoverflow.com/questions/976907/sending-cookies-from-c-sharp-application-to-an-internet-explorer-pop-up-windowhttp://stackoverflow.com/questions/8180113/how-to-open-a-browser-with-session-information-from-a-c-sharp-application(there are many more pages like these - maybe there is one with a better solution out there)

Ferdinand Prantl

Another solution would be writing you own login request handler accepting the login cookie you'd get by other means. For example:

http://bg-bim-cs10/otcs/livelink.exe?func=cookielogin&cookie=<cookie here>&nexturl=<document fetching URL here>

If you have pure CS without RCS you'd use your user token as the cookie as the others suggested. If you have RCS you'd get the cookie by the LAPI call GetCookieInfo or a WS method you find or write; your application runs on the same machine as the browser so that the cookie will work.

--- Ferda