Recently OT Dev said that don’t really spend time on the Search SOAP service but use the Restful search API that has been there all along these years.
Since almost everything in livelink is served off a URL one of the first things it needs is authentication.For livelink deployments who do not have Single Sign On based on web server auth it is inconvenient that a webapp designed in C# provides links to a livelink URL for e.g I may have an href called “My Assignments” and then I may link it to my livelink server url and the query string ending in personal .assignments
I really don’t think organizations using livelink still use userid/password but this will probably help those users.
Now everybody reading this should know that livelink will look for a cookie if not it will present a login screen. Our attempt is to use the token (cookie) returned to us by the CWS auth routine and make sure we can pass it off to a livelink URL or making the request to livelink as if one had logged in and subsequently performing operations.
In my example I am doing this with a LL 9.7.1 version so the ref key word is not used.For newer CWS the ref keyword is needed
LL9.7.1 Oracle,IIS6, webserver is anonymous,livelink auth scheme is livelink ,No RCS present,No Dir Svcs module in deployment
in SSO deployments calling a livelink URL from a auth user’s computer results in a pass thru experience so none of this circus is needed anyway.
What I found was if you were adding the LlCookie to the request you have to do a lot of coding as in the user in this thread.I found several hits in the web
to spoof the Cookie but a lot of code for somethingthat you know is not that secure anyway
RE RE RE RE RE Get Region Name
He first gets the auth token and uses cookie setting code to call the search API.
While that is all good and dandy if you have access to a web debugging tool like Fiddler if you capture traffic for the first auth call you can see your userid+password
if it is a HTTP connection.I am not sure what it will look if my livelink was HTTPS.So I would just build a userid/password url and specify everything in NextURL.
So if I was coding a C# app and wanted to call my search system in livelink I would just use the simple approach
In the above URL the Func=ll.login sets the Cookie and then the NextURL is indicated,it is just webescaped for transmission
3 thoughts on “How to use WCF Livelink web services to create a quasi single sign on or login with cookie equivalent of lapi”
Kyle gave a better explanation as in this thread here so you could use that method rather my userid/password method also https://knowledge.opentext.com/knowledge/cs.dll/open/42932531
Kindly share some documents and examples for implementing Using WCF Service to integrate with Live Link.
Upload and download the document through web service. (.Net)
Email : email@example.com
See this posting on where to find the software/examples etc.If you have a working livelink server you have the binaries for the WSDL sitting in the \webservices folder
https://appukili.wordpress.com/2014/10/18/what-is-enterprise-web-services-a-k-a-content-web-services/ then I would play with SOAPUI on some easy example found on the KB and start writing the .NET version