Impersonate through LAPI in Java

Is it possible to impersonate through the Java API ? I can see it's possible with Visual Basic as well as C++, but I don't want to use Visual Basic and preferrably not C++ either.

Find more posts tagged with

Comments

x-opconuser3_-_(deleted)

LLSession.ImpersonateUser(String userLogon) will do the trick.Too bad they didn't allow for this method to accept a password and do authentication. As it is now one must build a LLSession to authenticate.Makes the LAPI a more useless than OScript

eLink User

Message from chris meyer via eLinkImpersonateUser has a specific function: It allows admin users to accessLivelink in the context of a user. Authentication with username andpassword has a different purpose and requires a new LLSession to be built.Why does this make LAPI useless? Are you confusing the purpose of eachfunction?chris----- Original Message -----From: "eLink Discussion: LAPI Discussion" To: "eLink Recipient" Sent: Friday, August 23, 2002 4:52 PMSubject: Impersonating users> Impersonating users> Posted by OpConUser3 on 08/23/2002 10:39 AM>> LLSession.ImpersonateUser(String userLogon) will do the trick.>> Too bad they didn't allow for this method to accept a password and doauthentication. As it is now one must build a LLSession to authenticate.>> Makes the LAPI a more useless than OScript>> [To reply to this thread, use your normal e-mail reply function.]>> ============================================================>> Topic: Impersonate through LAPI in Java>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2828367&objAction=view>> Discussion: LAPI Discussion>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=view>> Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe>>>

x-opconuser3_-_(deleted)

I was too harsh in my criticism, it does not make it useless, but more difficult to work with in a specific scenario (that it seems many people would like to use).The scenario is using LAPI server-side in a Servlet, with a single logon/LLSession, using the ImpersonateUser method to broker requests to the system.Why do this? LAPI, from what our experts tell me, is not efficient in using system resources (something along the line of each LAPI session requires a Thread, and there are only 3 available to LAPI in the default configuration).Other reasons include the desire to NOT learn OScript and NOT to learn LLBuilder to design web applications based on Livelink (some people like to use non-proprietary tools and languages, ya know?).But wait!!! In browsing the Opentext classes, I see a Undocumented method (imagine that!) named ImpersonateUser(String, String), where the second parameter might be the password. I haven't had time to test this out.Could some expert at Opentext explain this undocumented method???Thanks,jk

eLink User

Message from chris meyer via eLinkHi jk,Each LLSession does not take up a thread. It's the actual request itself(independent of which session is issuing the request) that uses a Livelinkthread for the duration of that request. Once the request is complete, thethread sits idle until another request is made. In other words, I don't seeit necessary to use the ImpersonateUser() function outside the context ofadministration. I'm curious how your experts came to the conclusion thatthread usage was somehow session dependent. Remember, LAPI is statelessmuch like web requests are: What is normally stored inside your cookie(server, login, password info) is stored inside the LAPI session object.The three threads you have been quoted is the default number of Livelinkserver threads, which serves both LAPI and web server (CGI) requests. Thiscan be configured by the Livelink administrator.I hope this helps with your development. chris----- Original Message -----From: "eLink Discussion: LAPI Discussion" To: "eLink Recipient" Sent: Tuesday, August 27, 2002 3:10 PMSubject: I was too harsh in my criticism, it does not make it useless, butmore...> I was too harsh in my criticism, it does not make it useless, but more...> Posted by OpConUser3 on 08/27/2002 09:03 AM>> I was too harsh in my criticism, it does not make it useless, but moredifficult to work with in a specific scenario (that it seems many peoplewould like to use).>> The scenario is using LAPI server-side in a Servlet, with a singlelogon/LLSession, using the ImpersonateUser method to broker requests to thesystem.>> Why do this? LAPI, from what our experts tell me, is not efficient inusing system resources (something along the line of each LAPI sessionrequires a Thread, and there are only 3 available to LAPI in the defaultconfiguration).>> Other reasons include the desire to NOT learn OScript and NOT to learnLLBuilder to design web applications based on Livelink (some people like touse non-proprietary tools and languages, ya know?).>> But wait!!! In browsing the Opentext classes, I see a Undocumented method(imagine that!) named ImpersonateUser(String, String), where the secondparameter might be the password. I haven't had time to test this out.>> Could some expert at Opentext explain this undocumented method???>> Thanks,> jk>> [To reply to this thread, use your normal e-mail reply function.]>> ============================================================>> Topic: Impersonate through LAPI in Java>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2828367&objAction=view>> Discussion: LAPI Discussion>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=view>> Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe>>>