Setting Login Cookie through LAPI

Does anyone know of a way to set a Login cookie or some kind of session variable using LAPI so that when a user clicks a link to go into Livelink from a portal page, Livelink would already see them as logged in.We are trying to implement some single sign on features with Livelink being one of the applications that our users will have access to. We cannot use Livelinks Single Sign on Module.Any ideas would be greatly appreciated.

Find more posts tagged with

Comments

eLink User

Message from Magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Why can't you use Single sign on ?!?!?! Both in the Portal and in Livelink ???

What Portal , what plattforms , WEBservers are you using, Livelink versions ?!?!?

One is to "steal" and do the way Livelink does....:

Normal Livelink login

When a connection to Livelink is done Livelink testst if the session cookie is set.

If not then a redirection is done to the Login Page

Single sign on with IIS and Livelink Directory Service ....

If the users is using Single sign on Livelink trusts that the WEBserver ( if IIS is used)

has done the authorisation and sets the cookie

One way for you and your portal with authentiofication

When a connection is done and no session cookie is there. You take over and checks against your portal system

if the user is logged in. If not let him login to the portal. If yes the user is authentificated against the portal then set the cookie....

Another way is to see what has been done with Unite and if that could be reused or store. Have a look at the

today added Presentation TEC2034 Creating Filtered Maps in Livelink or Any Portal to Guide Your Users.ppt

Challenge (support LAPI / Livcelink Explorer applications)

Good luck

Magnus@ids.se

Van_Duong_(tridentadmin_-_(deleted))

According to our Admins, we are not able to use Single Sign on from Livelink because of the following:1) Users will have to use Internet Explorer (cannot force them to use certain browser)2) Livelink does only a one way account sync from NT to Livelink, so if there are preexisting Livelink accounts, not sure what the result will be (still needs more testing) We would need to use NTLM for this and not LDAP because we use IIS 4.0.3) Not all of the Livelink User profile fields are filled in during the sync from NT to LiveLink. Would still have to go back in by hand to fill in extra fields.4) Only able to place new users in one Ontime Timezone. Cannot have more then one timezone defined for the system.The biggest problem is the users only being able to use IE and cannot use Netscape. We host Livelink for several outside companies and cannot control what they use or what someone uses from home.We are using IIS 4.0 on NT 4.0 with Livelink 9.1. IIS 4.0 and NT are our standards and I don't see us changing anytime in the near future. We are writing out own simple portal which allows the user to have a starting point for many other applications that they have access to. Livelink is one of those applications.You stated the following:"When a connection is done and no session cookie is there. You take over and checks against your portal systemif the user is logged in. If not let him login to the portal. If yes the user is authentificated against the portal then set the cookie...."What would I check against my portal system. I cannot just check the portal user database because the passwords are stored with MD5 encryption which I'm not sure there is a way to decrypt. That is why I was trying to set some kind of cookie from the outside but did not know how to check it with oscript unless it's a livelink cookie.Hope that gives you an idea of what we are trying to do. I appreciate you taking time to give some suggestions. We are not the most experienced Livelink developers here so I appreciate all the help I can get.Thanks,Jeff RadkeVerdian Information Solutionsjeff.radke@veridian.com(310) 348-6372