| ||||||||||||
![]() |
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
(#1)
|
(#2)
|
| Senior Member Posts: 5,765 Join Date: Jun 2005 Location: Cumbria, UK |
26-04-2007, 04:39 PM
The way it works is :- 1. Kayako checks to see if LoginShare is active for that template group. If it isn't, load users directly from the DB. If it is, move to step 2. 2. Find out which LoginShare is used. At this point, it looks up loginshare.config.php, loginshare.php and the LoginShare file for the particular piece of software. 3. If it can access the DB ok, pull the user's details out of the 3rd party software DB. At this point, the details are sent back to the main system login file ready for actually allowing the user in. Hope this helps you. Icon Headquarters - Its Elixir - Web2Messenger |
| | |
(#3)
|
(#4)
|
| Senior Member Posts: 5,765 Join Date: Jun 2005 Location: Cumbria, UK |
26-04-2007, 07:18 PM
Oh right. Misread. includes/functions_users.php is what you need I think. It is the part that calls the LoginShare should it be needed. Icon Headquarters - Its Elixir - Web2Messenger |
| | |
(#5)
|
| Operations Manager Posts: 5,458 Join Date: Jan 2006 Location: United Kingdom |
26-04-2007, 07:19 PM
It is not possible to not set a LoginShare, in effect. The "default" or standard LoginShare module is in fact SupportSuite's own. Where this code is, I am unsure. You could submit a support ticket for the attention of a developer. however. -------------------------------------------------------------------
|
| | |
(#6)
|
| Senior Member Posts: 5,765 Join Date: Jun 2005 Location: Cumbria, UK |
26-04-2007, 08:35 PM
That functions_users.php handles it. It checks to see if a LoginShare is needed. If so, redirect to LoginShare files, if not use the code within that file to log the user in using Kayako's own database. Icon Headquarters - Its Elixir - Web2Messenger |
| | |
(#7)
|
(#8)
|
![]() |
| Tags |
| loginshare, scriptpart |
| Thread Tools | Search this Thread |
| Display Modes | |
| |