loginshare question

[bbutle01]

Ok, I've developed my own loginshare. It works... the first time only.

After a user logs out, they can't log in again.

I noticed that they are being added to swusers table and swuseremails... which I find odd. Is that normal behaviour when using a login share, or is that the problem?

If I delete them from those tables they can log in again, once...

[Salaria]

Hi, Here might be problem with your "loginShareAuthorize" function. Can you please paste here the code snippet or PM me to help you better.

Regards,
Mahesh Salaria

[Dewak]

LoginShare by default adds the user to the Kayako database if the user has been successfully authenticated on the external database.
You have to check your code and see what happens when your user exists on the external database and also exists on Kayako (this would be the second login attempt)

Best

[bbutle01]

thanks for the tip guys... The problem was mostly with the fact that I'm not md5ing the data... I've got two options the way I see it. Add a new md5password_usr field, and update it with an md5 version of the password, I'll do on a cron job... I can't easily put it in when the user is registered.

Or a view that instead of displaying password_usr, displays md5(password_usr).

I did the first option to test my code, and it worked, but I don't like a bunch of scripts running on cron jobs, so I think I'll do the second.