[GH-ISSUE #4282] Log Failed Authentication Attempts for HTTP Basic Auth on Dashboard [Feature Request] #3376

Closed
opened 2026-05-05 14:10:36 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @JmmyGun on GitHub (Jun 15, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4282

Describe the feature request

First, thank you for the excellent work on frp. It's an invaluable tool for many of us.

I would like to request a new feature for frps: the ability to log failed authentication attempts for HTTP Basic Auth on the dashboard. Currently, successful logins are logged, but failed attempts are not, which makes it difficult to monitor and enhance security.

Logging failed attempts would greatly aid in security monitoring and incident response. Additionally, this feature would allow the implementation of tools like fail2ban to further secure the system.

Thank you for considering this feature if it is possible.

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @JmmyGun on GitHub (Jun 15, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4282 ### Describe the feature request First, thank you for the excellent work on frp. It's an invaluable tool for many of us. I would like to request a new feature for frps: the ability to log failed authentication attempts for HTTP Basic Auth on the dashboard. Currently, successful logins are logged, but failed attempts are not, which makes it difficult to monitor and enhance security. Logging failed attempts would greatly aid in security monitoring and incident response. Additionally, this feature would allow the implementation of tools like fail2ban to further secure the system. Thank you for considering this feature if it is possible. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
Author
Owner

@fatedier commented on GitHub (Jun 17, 2024):

The features in this aspect is very good, including IP whitelists and blacklists, and we plan to support this in the future.

However, in the current version, we will not introduce such capabilities extensively. Instead, we aim to focus on architectural restructuring to facilitate the implementation of more non-core Layer 7 capabilities through plugins in the future.

<!-- gh-comment-id:2172073550 --> @fatedier commented on GitHub (Jun 17, 2024): The features in this aspect is very good, including IP whitelists and blacklists, and we plan to support this in the future. However, in the current version, we will not introduce such capabilities extensively. Instead, we aim to focus on architectural restructuring to facilitate the implementation of more non-core Layer 7 capabilities through plugins in the future.
Author
Owner

@JmmyGun commented on GitHub (Jun 17, 2024):

Thanks anyway for taking my feature into consideration, I look forward to future updates. and thanks again for the wonderful "frp"

<!-- gh-comment-id:2172086389 --> @JmmyGun commented on GitHub (Jun 17, 2024): Thanks anyway for taking my feature into consideration, I look forward to future updates. and thanks again for the wonderful "frp"
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3376
No description provided.