AD loginshare problem

[SMBuser]

I have enabled AD integration in Loginshare.
I spent some time on it and it seems working now.
However not the way I expected it.

When user goes to esupport page and types AD username and password - it works.

If he/she sends an email first and Email Parser retrieves the email and creates the ticket and the user in the esupport DB then AD username and password don't work.
I thought when user logs in it would re-write the temp password created by EmailParser with the one from AD. However it doesn’t.

I am pretty sure it worked before. With version 3.00.32 (or 3.00.80). (Maybe not )

Maybe I can fix it somehow in the settings?

[melo555]

I had the same problem
I contacted Kayako and they told me that local login does not work with AD.
So if the account is created automatically by the email parser, then the account is treated as local

the solution is the following:

go to Staff CP and check the user ID

then open the kayako mysql database (called swift) and do the following:

select loginapi_userid from swusers where userid='ID';

this will select the loginapi from ID (must replace ID with the ID number)
If you do this with an account created by an email you should get 0
if you do the same with an account that works, you should get the AD account login name (example: marc)

so the trick is to replace this 0 with the AD login name
for this do the following:

update swusers set loginapi_userid='hooli' where userid='ID';

again, must replace ID with the userId number


I suggest you do first a backup of the database

cheers

carmelo

[jamesM]

I had the very same problem people would send in a email and then go and try and login with there AD user name. I had about 20 support calls logged in the end I found the fastest way to fix the problem was to clear the the swusers table as well as the table that holds all the emails (sorry I can't remember the name but it would hold a table of emails addresses match back to userid in the swusers table. All the users when then able to login and see there logged tickets and no data was lost.

Of cuase before I tried this I tock a full back up and stopped the email parser just in case :-)

[eiden]

This happens becuase the LoginShare funtion has some drawbacks. Please read this post : Comments on LoginShare issue

[SMBuser]

Thanks, guys! You helped a lot!