Is anyone else getting this error consistently when they try to log on? We are having 10+ users a day getting this error even if it is the first time trying to log on for the day. Usually clearing cache and cookies fixes the issue, but that is no longer working. I have confirmed that the accounts are not locked. Is there something I am missing here?
Hi good morning - Most common challenges that we have seen are fat fingering and caching issues. I can't speak to any known challenges with direct authenticating that we have run into over the past 3.5 years with this approach. Maybe there was once a documented platform issue with the SSO at one point for a side of the organization but thats about it.
We do have our service desks acting as our backup and are supporting the reset of password as necessary for individuals and teams as necessary. Overall login has become a minimized concern as we are maturing the app at our organization.
Usually a password reset can clear these up but the user still needs to wait the allotted time before trying again...the admin cannot override the waiting period as far as I know.
Even with a password reset the same error is occurring. And they have not maxed out attempts as this will happen on their first try logging in. Usually clearing cache and cookies has fixed the issue and they no longer get the error but that fix seems to have stopped working.
As in enter a generic one and call out to the learner what the password is? And then enforce a password reset on next login with the option.
Some groups won’t support the approach of a generic pw for first use - but entering and saving a password for a user has to work.
Understood - so keep in mind what
Good luck with this one.
Um
Reply
Log in to Docebo Community
Enter your email address or username and password below to log in to Docebo Community. No account yet? Create an account
Docebo Employee Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.