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; } } }

Using java servlets+livelink with 1 login

Terence_Bieler

Hi,We are using Livelink for our intranet, next to this we havealso created some external applications (java servlets) that are available from the livelink menu. In our current situation, the user logs in using a javaservlet, and at the same time also logs in into livelink.If both logins are succesfull the user can use livelink andthe external applications.We are soon to be upgrading to Livelink 9.x and we want tomake the login process better, so the user only has to login once, and Livelink + the external applications knowwhich user has logged in. But how can we do this, I think the first step would be looking at the LAPI, but unfortunatly I havent been able tofind detailed information about this toppic.The ideal situation would be if the user logs in into Livelink,but how do the external java servlets know which user has beenlogged in?ps. the java servlets reside on the same machine as livelink,but a different webserver.Any advice is welcomeKind RegardsIdo

Find more posts tagged with

Comments

eLink User

Message from chris meyer via eLinkHi Ido,Do the servlets make any Livelink calls with LAPI?Why not use the same webserver for both applications such that the Livelink cookie can be read by the servlets? You may need to disable cookie encryption (a compromise), but this can be secured (to some degree) with SSL. chriseLink Discussion: LAPI Discussion wrote:>Using java servlets+livelink with 1 login>Posted by ErasmusAdmin on 02/17/2003 07:47 AM>>Hi,>We are using Livelink for our intranet, next to this we have>also created some external applications (java servlets) >that are available from the livelink menu.> >In our current situation, the user logs in using a java>servlet, and at the same time also logs in into livelink.>If both logins are succesfull the user can use livelink and>the external applications.>>We are soon to be upgrading to Livelink 9.x and we want to>make the login process better, so the user only has to >login once, and Livelink + the external applications know>which user has logged in. >But how can we do this, I think the first step would be >looking at the LAPI, but unfortunatly I havent been able to>find detailed information about this toppic.>>The ideal situation would be if the user logs in into Livelink,>but how do the external java servlets know which user has been>logged in?>ps. the java servlets reside on the same machine as livelink,>but a different webserver.>>Any advice is welcome>>Kind Regards>>Ido>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>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>>> >

Terence_Bieler

>>Do the servlets make any Livelink calls with LAPI? Not in our current situation, but we want to investigate the use of LAPI after we upgraded to the new LiveLink server to see ifthe servlets can be more integrated within our intranet (livelink)>>Why not use the same webserver for both applications such that the >>Livelink cookie can be read by the servlets? You may need to disable >>cookie encryption (a compromise), but this can be secured (to some >>degree) with SSL. chris Thanks for this tip, this option will certainly be looked at, howevernot encrypting the cookies concerns me a bit. Where can I find somedetailed information about LiveLink cookies, what info. is storedwithin them. What happens if the client browser has cookies switched off.Are there no other options to know which user has logged into livelinkfrom within java servlets? eg passing of sessions? RegardsIdo

eLink User

Message from chris meyer via eLinkHi,>>>Do the servlets make any Livelink calls with LAPI? >>> >>>>Not in our current situation, but we want to investigate the use >of LAPI after we upgraded to the new LiveLink server to see if>the servlets can be more integrated within our intranet (livelink)> >If you want the servlets to make connections to Livelink on behalf of your clients (e.g., authenticate AS your clients), you need to provide the user name and password to the servlet. This information is available in the cookie but is not accessable if you use encrypted cookies. On the otherhand, you can make a dummy user for specific servlet requets, but this does not provide personalized content to the user.>>>Why not use the same webserver for both applications such that the >>>Livelink cookie can be read by the servlets? You may need to disable >>>cookie encryption (a compromise), but this can be secured (to some >>>degree) with SSL. chris >>> >>>>Thanks for this tip, this option will certainly be looked at, however>not encrypting the cookies concerns me a bit. Where can I find some>detailed information about LiveLink cookies, what info. is stored>within them. What happens if the client browser has cookies switched off.>Try this. Change the wantSecureCookies flag in your opentext.ini to false. This should disable encrypted cookies. Login to Livelink and type the following into the address bar of the browser: javascript: alert(document.cookie) and hit enter. You will see how the cookie is built.>Are there no other options to know which user has logged into livelink>from within java servlets? eg passing of sessions?>You need some way of linking the servlet sessions to the Livelink sessions. My approach is to share the cookie information from the client. What do you normally authenticate your servlets against? chris

Terence_Bieler

Thanks for the detailed description, I guess the signinonce/sharing client info principle is the next step for web applications, as more different web apps want to work together, but appart from cookies, there arent that many "neat" solutions outthere. >>What do you normally authenticate your servlets against?We use LDAP and then server side sessions, no cookies.Thanks for allRegardsIdo

eLink User

Message from chris meyer via eLinkIsn't a cookie required such that the server-side session can be correctly linked to the user accessing the site? chriseLink Discussion: LAPI Discussion wrote:>Thanks for the detailed description, I guess the signin>Posted by ErasmusAdmin on 02/19/2003 03:50 AM>>Thanks for the detailed description, I guess the signin>once/sharing client info principle is the next step for web >applications, as more different web apps want to work >together, but appart from cookies, there arent that many "neat" solutions outthere. >> >>>>What do you normally authenticate your servlets against?>>> >>>>>We use LDAP and then server side sessions, no cookies.>>Thanks for all>>Regards>>Ido>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&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>>> >

Terence_Bieler

>>Isn't a cookie required such that the server-side session can be >>correctly linked to the user accessing the site? mm, dont know, this is something that my servlet handlesinternaly. But come to think of it, it could indeed usecookies to store a unique session id for per user.

eLink User

Message from Armstrong, Rusty (OE) via eLinkI was following this thread and was curious. I looked in out ini and donot see a wantsecurecookie flag. I assume it defaults to true but whatsection should it be in?Thanks-----Original Message-----From: eLink Discussion: LAPI Discussion[mailto:lapi@elinkkc.opentext.com] Sent: Tuesday, February 18, 2003 8:57 AMTo: eLink RecipientSubject: Re >>Do the servlets make any Livelink calls with LAPI?Re >>Do the servlets make any Livelink calls with LAPI?Posted by eLink on 02/18/2003 09:56 AMMessage from chris meyer via eLinkHi,>>>Do the servlets make any Livelink calls with LAPI?>>> >>>>Not in our current situation, but we want to investigate the use>of LAPI after we upgraded to the new LiveLink server to see if>the servlets can be more integrated within our intranet (livelink)> >If you want the servlets to make connections to Livelink on behalf of your clients (e.g., authenticate AS your clients), you need to provide the user name and password to the servlet. This information is available in the cookie but is not accessable if you use encrypted cookies. On the otherhand, you can make a dummy user for specific servlet requets, but this does not provide personalized content to theuser.>>>Why not use the same webserver for both applications such that the>>>Livelink cookie can be read by the servlets? You may need to disable >>>cookie encryption (a compromise), but this can be secured (to some >>>degree) with SSL. chris >>> >>>>Thanks for this tip, this option will certainly be looked at, however >not encrypting the cookies concerns me a bit. Where can I find some >detailed information about LiveLink cookies, what info. is stored >within them. What happens if the client browser has cookies switched >off.>Try this. Change the wantSecureCookies flag in your opentext.ini to false. This should disable encrypted cookies. Login to Livelink and type the following into the address bar of the browser: javascript: alert(document.cookie) and hit enter. You will see how the cookie is built.>Are there no other options to know which user has logged into livelink >from within java servlets? eg passing of sessions?>You need some way of linking the servlet sessions to the Livelink sessions. My approach is to share the cookie information from the client. What do you normally authenticate your servlets against? chris[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: Using java servlets+livelink with 1 loginhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&objAction=viewDiscussion: LAPI Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink Server: https://knowledge.opentext.com/knowledge/livelink.exe+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Sasol eMail disclaimer which may be found at: http://www.sasol.com/disclaimer.htm.If you cannot access the disclaimer through the URL attached and you wish to receive a copy thereof please send an eMail to disclaimer@sasol.com. You will receive the disclaimer by return eMail.+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

eLink User

Message from chris meyer via eLinkHi Rusty,I believe it defaults to true in all cases unless it is specifically set to false. The flag may not appear in all versions of Livelink, but it is set in my Livelink v9.1.0.3 installation. cheers, chriseLink Discussion: LAPI Discussion wrote:>RE Re >>Do the servlets make any Livelink calls with LAPI?>Posted by eLink on 02/20/2003 11:24 AM>>Message from Armstrong, Rusty (OE) via eLink>>>I was following this thread and was curious. I looked in out ini and do>not see a wantsecurecookie flag. I assume it defaults to true but what>section should it be in?>>Thanks>>-----Original Message----->From: eLink Discussion: LAPI Discussion>[mailto:lapi@elinkkc.opentext.com] >Sent: Tuesday, February 18, 2003 8:57 AM>To: eLink Recipient>Subject: Re >>Do the servlets make any Livelink calls with LAPI?>>>Re >>Do the servlets make any Livelink calls with LAPI?>Posted by eLink on 02/18/2003 09:56 AM>>Message from chris meyer via eLink>>Hi,>> >>>>>Do the servlets make any Livelink calls with LAPI?>>>> >>>>>>>> >>>>>>Not in our current situation, but we want to investigate the use>>of LAPI after we upgraded to the new LiveLink server to see if>>the servlets can be more integrated within our intranet (livelink)>> >>>> >>>If you want the servlets to make connections to Livelink on behalf of >your clients (e.g., authenticate AS your clients), you need to provide >the user name and password to the servlet. This information is >available in the cookie but is not accessable if you use encrypted >cookies. On the otherhand, you can make a dummy user for specific >servlet requets, but this does not provide personalized content to the>user.>> >>>>>Why not use the same webserver for both applications such that the>>>>Livelink cookie can be read by the servlets? You may need to disable >>>>cookie encryption (a compromise), but this can be secured (to some >>>>degree) with SSL. chris >>>> >>>>>>>> >>>>>>Thanks for this tip, this option will certainly be looked at, however >>not encrypting the cookies concerns me a bit. Where can I find some >>detailed information about LiveLink cookies, what info. is stored >>within them. What happens if the client browser has cookies switched >>off.>>>> >>>Try this. Change the wantSecureCookies flag in your opentext.ini to >false. This should disable encrypted cookies. Login to Livelink and >type the following into the address bar of the browser: javascript: >alert(document.cookie) and hit enter. You will see how the cookie is >built.>> >>>Are there no other options to know which user has logged into livelink >> >>>>from within java servlets? eg passing of sessions?> >>You need some way of linking the servlet sessions to the Livelink >sessions. My approach is to share the cookie information from the >client. What do you normally authenticate your servlets against? chris>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967>931&objAction=view>>Discussion: LAPI Discussion>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=7654>28&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>NOTICE: Please note that this eMail, and the contents thereof, >is subject to the standard Sasol eMail disclaimer which may be >found at: http://www.sasol.com/disclaimer.htm.>>If you cannot access the disclaimer through the URL attached and >you wish to receive a copy thereof please send an eMail to >disclaimer@sasol.com. You will receive the disclaimer by return eMail.>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&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>>> >

eLink User

Message from Armstrong, Rusty (OE) via eLinkChris-----Original Message-----From: eLink Discussion: LAPI Discussion[mailto:lapi@elinkkc.opentext.com] Sent: Thursday, February 20, 2003 10:42 AMTo: eLink RecipientSubject: Re RE Re >>Do the servlets make any Livelink calls with LAPI?Re RE Re >>Do the servlets make any Livelink calls with LAPI? Postedby eLink on 02/20/2003 11:42 AMMessage from chris meyer via eLinkHi Rusty,I believe it defaults to true in all cases unless it is specifically setto false. The flag may not appear in all versions of Livelink, but it is set in my Livelink v9.1.0.3 installation. cheers, chriseLink Discussion: LAPI Discussion wrote:>RE Re >>Do the servlets make any Livelink calls with LAPI? Posted by >eLink on 02/20/2003 11:24 AM>>Message from Armstrong, Rusty (OE) via >eLink>>>I was following this thread and was curious. I looked in out ini and do>not see a wantsecurecookie flag. I assume it defaults to true but what >section should it be in?>>Thanks>>-----Original Message----->From: eLink Discussion: LAPI Discussion >[mailto:lapi@elinkkc.opentext.com]>Sent: Tuesday, February 18, 2003 8:57 AM>To: eLink Recipient>Subject: Re >>Do the servlets make any Livelink calls with LAPI?>>>Re >>Do the servlets make any Livelink calls with LAPI? Posted by >eLink on 02/18/2003 09:56 AM>>Message from chris meyer via eLink>>Hi,>> >>>>>Do the servlets make any Livelink calls with LAPI?>>>> >>>>>>>> >>>>>>Not in our current situation, but we want to investigate the use of >>LAPI after we upgraded to the new LiveLink server to see if the >>servlets can be more integrated within our intranet (livelink)>> >>>> >>>If you want the servlets to make connections to Livelink on behalf of>your clients (e.g., authenticate AS your clients), you need to provide >the user name and password to the servlet. This information is >available in the cookie but is not accessable if you use encrypted >cookies. On the otherhand, you can make a dummy user for specific >servlet requets, but this does not provide personalized content to the>user.>> >>>>>Why not use the same webserver for both applications such that the >>>>Livelink cookie can be read by the servlets? You may need to disable>>>>cookie encryption (a compromise), but this can be secured (to some>>>>degree) with SSL. chris>>>> >>>>>>>> >>>>>>Thanks for this tip, this option will certainly be looked at, however>>not encrypting the cookies concerns me a bit. Where can I find some >>detailed information about LiveLink cookies, what info. is stored >>within them. What happens if the client browser has cookies switched >>off.>>>> >>>Try this. Change the wantSecureCookies flag in your opentext.ini to>false. This should disable encrypted cookies. Login to Livelink and >type the following into the address bar of the browser: javascript: >alert(document.cookie) and hit enter. You will see how the cookie is >built.>> >>>Are there no other options to know which user has logged into livelink>> >>>>from within java servlets? eg passing of sessions?> >>You need some way of linking the servlet sessions to the Livelink>sessions. My approach is to share the cookie information from the >client. What do you normally authenticate your servlets against?chris>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>7>931&objAction=view>>Discussion: LAPI Discussion >https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>4>28&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>NOTICE: Please note that this eMail, and the contents thereof,>is subject to the standard Sasol eMail disclaimer which may be >found at: http://www.sasol.com/disclaimer.htm.>>If you cannot access the disclaimer through the URL attached and>you wish to receive a copy thereof please send an eMail to >disclaimer@sasol.com. You will receive the disclaimer by return eMail.>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>7931&objAction=view>>Discussion: LAPI Discussion >https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>428&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>> >[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: Using java servlets+livelink with 1 loginhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&objAction=viewDiscussion: LAPI Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink Server: https://knowledge.opentext.com/knowledge/livelink.exe+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Sasol eMail disclaimer which may be found at: http://www.sasol.com/disclaimer.htm.If you cannot access the disclaimer through the URL attached and you wish to receive a copy thereof please send an eMail to disclaimer@sasol.com. You will receive the disclaimer by return eMail.+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

eLink User

Message from Armstrong, Rusty (OE) via eLinkThanks. We are running 9.1(sp1). Do you know which section it should bein? General? Option? Something else?Rusty-----Original Message-----From: eLink Discussion: LAPI Discussion[mailto:lapi@elinkkc.opentext.com] Sent: Thursday, February 20, 2003 10:42 AMTo: eLink RecipientSubject: Re RE Re >>Do the servlets make any Livelink calls with LAPI?Re RE Re >>Do the servlets make any Livelink calls with LAPI? Postedby eLink on 02/20/2003 11:42 AMMessage from chris meyer via eLinkHi Rusty,I believe it defaults to true in all cases unless it is specifically setto false. The flag may not appear in all versions of Livelink, but it is set in my Livelink v9.1.0.3 installation. cheers, chriseLink Discussion: LAPI Discussion wrote:>RE Re >>Do the servlets make any Livelink calls with LAPI? Posted by >eLink on 02/20/2003 11:24 AM>>Message from Armstrong, Rusty (OE) via >eLink>>>I was following this thread and was curious. I looked in out ini and do>not see a wantsecurecookie flag. I assume it defaults to true but what >section should it be in?>>Thanks>>-----Original Message----->From: eLink Discussion: LAPI Discussion >[mailto:lapi@elinkkc.opentext.com]>Sent: Tuesday, February 18, 2003 8:57 AM>To: eLink Recipient>Subject: Re >>Do the servlets make any Livelink calls with LAPI?>>>Re >>Do the servlets make any Livelink calls with LAPI? Posted by >eLink on 02/18/2003 09:56 AM>>Message from chris meyer via eLink>>Hi,>> >>>>>Do the servlets make any Livelink calls with LAPI?>>>> >>>>>>>> >>>>>>Not in our current situation, but we want to investigate the use of >>LAPI after we upgraded to the new LiveLink server to see if the >>servlets can be more integrated within our intranet (livelink)>> >>>> >>>If you want the servlets to make connections to Livelink on behalf of>your clients (e.g., authenticate AS your clients), you need to provide >the user name and password to the servlet. This information is >available in the cookie but is not accessable if you use encrypted >cookies. On the otherhand, you can make a dummy user for specific >servlet requets, but this does not provide personalized content to the>user.>> >>>>>Why not use the same webserver for both applications such that the >>>>Livelink cookie can be read by the servlets? You may need to disable>>>>cookie encryption (a compromise), but this can be secured (to some>>>>degree) with SSL. chris>>>> >>>>>>>> >>>>>>Thanks for this tip, this option will certainly be looked at, however>>not encrypting the cookies concerns me a bit. Where can I find some >>detailed information about LiveLink cookies, what info. is stored >>within them. What happens if the client browser has cookies switched >>off.>>>> >>>Try this. Change the wantSecureCookies flag in your opentext.ini to>false. This should disable encrypted cookies. Login to Livelink and >type the following into the address bar of the browser: javascript: >alert(document.cookie) and hit enter. You will see how the cookie is >built.>> >>>Are there no other options to know which user has logged into livelink>> >>>>from within java servlets? eg passing of sessions?> >>You need some way of linking the servlet sessions to the Livelink>sessions. My approach is to share the cookie information from the >client. What do you normally authenticate your servlets against?chris>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>7>931&objAction=view>>Discussion: LAPI Discussion >https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>4>28&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>NOTICE: Please note that this eMail, and the contents thereof,>is subject to the standard Sasol eMail disclaimer which may be >found at: http://www.sasol.com/disclaimer.htm.>>If you cannot access the disclaimer through the URL attached and>you wish to receive a copy thereof please send an eMail to >disclaimer@sasol.com. You will receive the disclaimer by return eMail.>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>7931&objAction=view>>Discussion: LAPI Discussion >https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>428&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>> >[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: Using java servlets+livelink with 1 loginhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&objAction=viewDiscussion: LAPI Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink Server: https://knowledge.opentext.com/knowledge/livelink.exe+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard Sasol eMail disclaimer which may be found at: http://www.sasol.com/disclaimer.htm.If you cannot access the disclaimer through the URL attached and you wish to receive a copy thereof please send an eMail to disclaimer@sasol.com. You will receive the disclaimer by return eMail.+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

eLink User

Message from chris meyer via eLinkI think it's in the [options] section. chriseLink Discussion: LAPI Discussion wrote:>RE Re RE Re >>Do the servlets make any Livelink calls with LAPI? 2>Posted by eLink on 02/20/2003 12:32 PM>>Message from Armstrong, Rusty (OE) via eLink>>>Thanks. We are running 9.1(sp1). Do you know which section it should be>in? General? Option? Something else?>>Rusty>>-----Original Message----->From: eLink Discussion: LAPI Discussion>[mailto:lapi@elinkkc.opentext.com] >Sent: Thursday, February 20, 2003 10:42 AM>To: eLink Recipient>Subject: Re RE Re >>Do the servlets make any Livelink calls with LAPI?>>>Re RE Re >>Do the servlets make any Livelink calls with LAPI? Posted>by eLink on 02/20/2003 11:42 AM>>Message from chris meyer via eLink>>Hi Rusty,>>I believe it defaults to true in all cases unless it is specifically set>>to false. The flag may not appear in all versions of Livelink, but it >is set in my Livelink v9.1.0.3 installation. cheers, chris>>>eLink Discussion: LAPI Discussion wrote:>> >>>RE Re >>Do the servlets make any Livelink calls with LAPI? Posted by >>eLink on 02/20/2003 11:24 AM>>>>Message from Armstrong, Rusty (OE) via >>eLink>>>>>>I was following this thread and was curious. I looked in out ini and do>> >>>> >>>not see a wantsecurecookie flag. I assume it defaults to true but what >>section should it be in?>>>>Thanks>>>>-----Original Message----->>From: eLink Discussion: LAPI Discussion >>[mailto:lapi@elinkkc.opentext.com]>>Sent: Tuesday, February 18, 2003 8:57 AM>>To: eLink Recipient>>Subject: Re >>Do the servlets make any Livelink calls with LAPI?>>>>>>Re >>Do the servlets make any Livelink calls with LAPI? Posted by >>eLink on 02/18/2003 09:56 AM>>>>Message from chris meyer via eLink>>>>Hi,>>>> >>>> >>>>>>>Do the servlets make any Livelink calls with LAPI?>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>Not in our current situation, but we want to investigate the use of >>>LAPI after we upgraded to the new LiveLink server to see if the >>>servlets can be more integrated within our intranet (livelink)>>>>>>>>> >>>>>> >>>>>If you want the servlets to make connections to Livelink on behalf of>>your clients (e.g., authenticate AS your clients), you need to provide >>the user name and password to the servlet. This information is >>available in the cookie but is not accessable if you use encrypted >>cookies. On the otherhand, you can make a dummy user for specific >>servlet requets, but this does not provide personalized content to the>>user.>>>> >>>> >>>>>>>Why not use the same webserver for both applications such that the >>>>>Livelink cookie can be read by the servlets? You may need to disable>>>>> >>>>>>> >>>>>>cookie encryption (a compromise), but this can be secured (to some>>>>>degree) with SSL. chris>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>Thanks for this tip, this option will certainly be looked at, however>>>not encrypting the cookies concerns me a bit. Where can I find some >>>detailed information about LiveLink cookies, what info. is stored >>>within them. What happens if the client browser has cookies switched >>>off.>>>>>> >>>>>> >>>>>Try this. Change the wantSecureCookies flag in your opentext.ini to>>false. This should disable encrypted cookies. Login to Livelink and >>type the following into the address bar of the browser: javascript: >>alert(document.cookie) and hit enter. You will see how the cookie is >>built.>>>> >>>> >>>>>Are there no other options to know which user has logged into livelink>>> >>>>>> >>>>>>from within java servlets? eg passing of sessions?>> >>>>You need some way of linking the servlet sessions to the Livelink>>sessions. My approach is to share the cookie information from the >>client. What do you normally authenticate your servlets against?>> >>>chris> >>>[To reply to this thread, use your normal e-mail reply function.]>>>>============================================================>>>>Topic: Using java servlets+livelink with 1 login>>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>>7>>931&objAction=view>>>>Discussion: LAPI Discussion >>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>>4>>28&objAction=view>>>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>>>NOTICE: Please note that this eMail, and the contents thereof,>>is subject to the standard Sasol eMail disclaimer which may be >>found at: http://www.sasol.com/disclaimer.htm.>>>>If you cannot access the disclaimer through the URL attached and>>you wish to receive a copy thereof please send an eMail to >>disclaimer@sasol.com. You will receive the disclaimer by return eMail.>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>>>[To reply to this thread, use your normal e-mail reply function.]>>>>============================================================>>>>Topic: Using java servlets+livelink with 1 login>>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=296>>7931&objAction=view>>>>Discussion: LAPI Discussion >>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765>>428&objAction=view>>>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>>> >>>> >>>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967>931&objAction=view>>Discussion: LAPI Discussion>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=7654>28&objAction=view>>Livelink Server: https://knowledge.opentext.com/knowledge/livelink.exe>>>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>NOTICE: Please note that this eMail, and the contents thereof, >is subject to the standard Sasol eMail disclaimer which may be >found at: http://www.sasol.com/disclaimer.htm.>>If you cannot access the disclaimer through the URL attached and >you wish to receive a copy thereof please send an eMail to >disclaimer@sasol.com. You will receive the disclaimer by return eMail.>>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Using java servlets+livelink with 1 login>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2967931&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>>> >