-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bolts getting locked out #25
Comments
xurizaemon
added a commit
to xurizaemon/hubot-matteruser
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
to xurizaemon/mattermost-client
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
to xurizaemon/mattermost-client
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
to xurizaemon/mattermost-client
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
to xurizaemon/mattermost-client
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
to xurizaemon/mattermost-client
that referenced
this issue
Apr 28, 2018
xurizaemon
added a commit
that referenced
this issue
Apr 29, 2018
Process to get bolts back in after a lockout:
|
(could be done by password reset also I think, but quicker via admin UI) |
Hmm, this happened again recently, after 18mo of not happening. Poop. |
Process to get bolts back in after a lockout:
|
Fixed with move to bot user and token auth |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bolts gets locked out (not logged out) for "too many password attempts" and can't reauthenticate.
I suspect this might be the same as #15 - something triggers a login cycle ahead of schedule? And we spam logins and get locked.
Mattermost config.json has
MaximumLoginAttempts
variable.The text was updated successfully, but these errors were encountered: