[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[feature] Option to configure disabling of users after failed login attempts #1045

Closed
MalteT opened this issue Mar 5, 2019 · 1 comment
Closed

[feature] Option to configure disabling of users after failed login attempts #1045

MalteT opened this issue Mar 5, 2019 · 1 comment
Labels
feature Adding a new feature, or substantial improvements on existing functionality

Comments

@MalteT
Copy link
MalteT commented Mar 5, 2019

Jellyfin currently disables a user after a couple of failed login attempts (I think 3). This is especially hurtful for admin accounts, because you have to search for the right /config/config/users/[gibberish]/policy.xml to enable the account again.

If the Jellyfin setup is accessible from WAN, third parties might just spam login attempts to constantly block you from using Jellyfin, because a blocked user gets logged out on all devices.

I would like to be able to disable the auto-disable funtion for specific users and if possible configure the amount of failed logins before the user gets disabled. (Some timeout between login attempts would be nice)

#870 might already address some of the these.
@anthonylavado anthonylavado added the feature Adding a new feature, or substantial improvements on existing functionality label Mar 7, 2019
@LogicalPhallacy
Copy link
Contributor

This is fixed in master, it will be in the upcoming 10.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Adding a new feature, or substantial improvements on existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@anthonylavado @MalteT @LogicalPhallacy