Can anyone share your action and filter files for implementing fail2ban on JIRA.
I was trying to configure fail2ban on our system and looking for best methods for implementing it effectively.
Any help is highly appreciated.........
The confluence documentation (https://confluence.atlassian.com/adminjiraserver073/using-fail2ban-to-limit-login-attempts-861253903.html) is half-baked and might lock you out with successful login attempts. Also the GET definition seems wrong.
The jail definition in filter.d will work with this (checked on v7.6.2 and Fail2ban 0.9.3)
----------
[Definition]
failregex = <HOST>.*"POST /rest/gadget/1.0/login HTTP/1.1" 200 219
<HOST>.*"POST /login.jsp HTTP/1.1" 200
ignoreregex=
----------
#1: this is using the fact that the message size is 220 when it succeeds and 219 when it fails
#2: this is using the fact that a sucessful login will return 302 (redirect) while it returns 200 if the login fails
YMMV
Thanks for replying but there regular expressions will trigger only for almost every login page countfailregex = <HOST>.*"GET
/login
.jsp
but we need these alerts to be triggered based on incorrect counts and not on login page count.
For example if you use above failregex then count will be increased as soon as you open a new tab and enter JIRA login URL.
I had gone through Justin link as well and also added my question(comment) yesterday itself.
So I needed something which has better implementation of filters to encounter all intruders.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure if I'm missing something, but google took me to this:
https://confluence.atlassian.com/display/JIRA/Using+Fail2Ban+to+limit+login+attempts
Some more info from the comments on that page: http://justinit.wordpress.com/2011/04/12/setup-fail2ban-for-jira-and-confluence/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.