Home
Extended ECM
API, SDK, REST and Web Services
No Log-out feature in Directory Services?
Marcia_Gillespie-Norder_(tokeleadmin_-_(deleted))
Hi,When you install the Directory Services module, you no longer get a Log-out option to log the user off the system. Instead, it seems the only way is to completely kill the browser. And, if a user has multiple browers open, this could be a problem.For one of our instances, they make some use of "role" users where an individual actually has one account for most work and a different account for other work. Lovely, eh?Anyway, they can use single-sign on for their normal network account. To log on to their "role" account, they have to go through a separate port. That is fine. However, they are having to kill all their browser sessions in order to log in properly. I think this has something to do with a cookie or something that Livelink is sending.My question:Is there any way to force a log out for a user when Directory Services module is installed?This particular question refers to the following configuration:Livelink 9.1.3Livelink Directory Services 2.2.2NTLM Authentication (no Synchronization)note: we also have a custom module (that I created) to prevent the resetPasswords function from resetting the passwords of our "role" users.Cheers,Kevin HutsonTokyo Electron America
Find more posts tagged with
Comments
Magnus_S_(novnoruser_-_(deleted))
The concept with singel signon is that when e.g. you log in to Windows you also get an unique ID and that is is you ....If the IIS doesn't recognize your credential from the windows login you get a sign in to the IIS.....So loging out means that you should log out from Windows .....My suggestion===========You should instead give the user the rights of the role so he/she can work under his/hers right identity but with the privs of the role....FYI There are possibilities in WF to support roles using Livelink Builder ==> a step is assigned a role and this role is translated when a WF moves to this step to an username that has this role .....Ps. I think you need to "reset" the IIS if you need a logout function as Livelink always trust a user that comes from the IIS and just sets a cookie in the user browser based on the pregenerated Livelink password .....
Geoff_Obbard
Message from Geoff Obbard <
gobbard@opentext.com
> via eLink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink
Hi Kevin,
If you must have two logins for these users, a simple way around this would be to set up a second Livelink instance on the same server pointing to the same database. Since the service name and CGI mapping will have to be different, and Livelink sets cookies that only return to the specific CGI mapping, the browser will not share cookies between the two instances. Users will be able to log in to both instances at the same time using different credentials.
As for your logout question, Directory Services removes the option to logout as the default behaviour would simply return the user to their default workspace ( Livelink unsets the cookie and directs the user to the cgi, the cgi detects that there is no cookie so logs the user in from remote_user, the user is then directed to their default workspace). If you wish to restore the log-out button, you could customize Livelink to redirect the user to a custom page on logout.
Geoff