vicidial.org

Vicibox 7.0.2 from .iso | Vicidial 2.12-557a Build 160517-1927 | Asterisk 11.21.2-vici | CLuster setup: 1 web 1 DB 5 telephony | No Digium/Sangoma Hardware | No Extra Software After Installation

has anyone ran into the same problem:

We have users that change seats quite often and once a user clocks into the timeclock feature of vici .. ONLY that user will be able to clock in from that browser unless you completely reset refresh or uninstall and reinstall the browser. I tried it with both chrome and firefox. After the initial clockin and clock out if you change to a different user then you get the user/password is incorrect prompt. Ive tried every possible way with saving user info not saving user info clearing browser history clear all saved logins. Any thoughts? Anyone else encountered this?

It looks like:

1) Your users do not login into OS and share/reuse the same OS user
2) Browser suggest users to store their vicidial credentials, and they happily save them. The credentials are stored in the browser settings within the same OS user profile.
3) Brower automatically inserts saved (wrong) credentials regardless of which vicidial user is actually using workstation


Suggestions:
-- clear browser stored password cache (no need to reinstall)
-- get users to login into OS with unique credentials for having different profiles and individual browser caches.

Regards,
Gene

Eugene,
thank you for your reply

1) Your users do not login into OS and share/reuse the same OS user

yes all the PC's have "generic" accounts because of the high turnover rate

2) Browser suggest users to store their vicidial credentials, and they happily save them. The credentials are stored in the browser settings within the same OS user profile.

yes they do however i tried every possible angle by deleting history, cache, and all saved within that browser. Tried refreshing/resetting the browser to defaults and also completely uninstalled and reinstalled with no success.

Come to find out Vicidial will log the ip address and when someone clocks in to the it appears that within that shift a different agent cant clock in there .. still need to test more to be 100%