Buzz: Questions & Answers

Good morning Jill,

I’m not seeing any of your user accounts currently locked out in Buzz. A Buzz lockout only occurs after the number of failed native login attempts defined in your domain settings has been exceeded (this would apply to direct Buzz logins, not SSO).

I do see that you have multiple user accounts across different domains, and some of those domains are configured to use CAS SSO authentication. If you’re experiencing access issues, it’s possible the lockout or authentication block is occurring at the SSO provider level rather than within Buzz itself.

Could you share the specific user ID and the approximate date/time of the most recent lockout? That will help us investigate further and determine where the issue may be occurring.

First, thank you for being so quick with your response! I may be using the wrong terms. I just had a student that reached out because his account was locked out. I took a screenshot of the error message for you. After he told me he was locked out, I went to my account and hit "Reset Lockout". 

I was assuming that the user accounts needed to be reset because the user was inactive for too long after I created the account. 

One user that is currently locked out is Natalie.Deegan, if that helps. 

Again, thank you for being so quick. I appreciate any assistance you can offer. 

Hi Jill,

I took a look at the domain where that user account resides (205816158), and it’s currently configured to automatically lock accounts if they haven’t authenticated in Buzz for 30 days. This means that if a user in that domain hasn’t logged in within 30 days, Buzz will automatically lock their account.

If you’d like to prevent that from happening as quickly, you can increase the number of days in the domain settings before the auto-lock is enforced.

The good news is that this user’s account has since been reset and they were able to authenticate to Buzz successfully.

I knew I was doing something wrong. Thank you so much!