Comments on LoginShare issue

eiden · **Comments on LoginShare issue -** 14-06-2006, 04:54 PM

I have added a task in the bugtracker: http://bugs.kayako.net/?do=details&id=1499

Does anyone have some comments or experience with this issue ?

brygrant · **same problem -** 22-06-2006, 07:06 AM

I have the same issue here. Trying to find a way around it. I got around them emailing in and it creating a user in the same mannor by changing it to manual verification (but it auto-veririfies them if they use AD loginshare anyway) and then setting the task C:\local\bin\wget.exe -q -O nul "http://orderdesk/cron/index.php?_t=crondailycleanup" to be run every 2 minutes. I'm only implementing for a small number of users (about 100) so it's not massive overheads when it runs it, but no doubt if you have significantly more it'll cause performance issues.

If I find anything else I'll post it on. Thanks for reporting the bug, I'd be interested in a fix. Or at least to see if we can have them added as unverified when a staff member (engineer) logs the call manually.

AKL-MFCU · **i would really -** 23-06-2006, 09:44 PM

i would really like to see this happen as well. Some of our, well, older staff, don't like change and so going to a web interface is too much for them. However, if we can have it so that they can e-mail and it works properly if they ever do login in, then that would be great. I don't see why its defaulting to a kayako username and password and not using ldap to authenticate like normal.

brygrant · **the way it works ... but no solution as yet -** 28-06-2006, 05:57 AM

Hi there AKL-MFCU. I agree about this should be available, for info the way it works in the login share is it takes the username and looks up using LDAP in active directory and grabs the details - such as username, display name, email address(es) and password. It then tries to authenticate using that email address in the database - ONLY if the email address (aka the Kayako user) does not exist does it use the LDAP AD details to create a user. If it does exist it just tries to use the one that's there.

I'll post more findings here if I get any. Hopefully either I or somebody else out there will find a way around this.

SMBuser · 29-06-2006, 11:45 PM

I too would love to have the issue fixed in some of the future releases!

jamesM · 30-06-2006, 03:44 AM

I will also say that this would be nice to have fixed :-)

craigbrass · 01-07-2006, 02:36 PM

Hello,

I have alerted Varun to this bug.

Best Regards,
Craig Brass

MadLuka · 25-07-2006, 01:18 PM

Still would be nice to have this fixed - the problem is still present in v3.0.0.90.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Require Validated Users to leave Comments	NC Software	Duplicate Requests	5	09-11-2007 11:02 AM
How do I disable Comments for KB and News areas?	NC Software	How do I?	10	03-12-2006 09:21 AM
LoginShare issues?	threeyears	SupportSuite, eSupport and LiveResponse	5	21-11-2006 01:17 PM

eiden Offline Member Posts: 237 Join Date: Apr 2006 Location: Norway	Comments on LoginShare issue - 14-06-2006, 04:54 PM I have added a task in the bugtracker: http://bugs.kayako.net/?do=details&id=1499 Does anyone have some comments or experience with this issue ?

SMBuser Offline New Member Posts: 5 Join Date: Jun 2006	29-06-2006, 11:45 PM I too would love to have the issue fixed in some of the future releases!

jamesM Offline Member Posts: 51 Join Date: Jun 2006	30-06-2006, 03:44 AM I will also say that this would be nice to have fixed :-)

craigbrass Online Senior Member Posts: 5,579 Join Date: Jun 2005 Location: Cumbria, UK	01-07-2006, 02:36 PM Hello, I have alerted Varun to this bug. Best Regards, Craig Brass Craig Brass - Kayako Forum Squatter (Note: I am NOT a staff member) Icon Headquarters - Its Elixir - Web2Messenger

MadLuka Offline Member Posts: 33 Join Date: Apr 2004	25-07-2006, 01:18 PM Still would be nice to have this fixed - the problem is still present in v3.0.0.90.