Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
Description
As a Confluence administrator, we would like to have a way to track the user login attempt for security reasons. It will be great to have the similar as in JIRA:
2014-07-25 17:34:55,755 http-bio-8080-exec-1 anonymous 1054x18749x1 18b3p1m 172.31.14.93,0:0:0:0:0:0:0:1 /rest/gadget/1.0/login login : 'captain.planet' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie. 2014-07-25 17:34:55,769 http-bio-8080-exec-1 anonymous 1054x18749x1 18b3p1m 172.31.14.93,0:0:0:0:0:0:0:1 /rest/gadget/1.0/login The user 'captain.planet' has FAILED authentication. Failure count equals 1 2014-07-25 17:34:55,770 http-bio-8080-exec-1 anonymous 1054x18749x1 18b3p1m 172.31.14.93,0:0:0:0:0:0:0:1 /rest/gadget/1.0/login Gadget login called with lastLoginResult : com.atlassian.jira.bc.security.login.LoginResultImpl@276896a0[reason=AUTHENTICATED_FAILED,loginInfo=com.atlassian.jira.bc.security.login.LoginInfoImpl@3a851475[lastLoginTime=1406072369469,previousLoginTime=1405985220323,loginCount=577,currentFailedLoginCount=1,totalFailedLoginCount=101,lastFailedLoginTime=1406273695756,elevatedSecurityCheckRequired=false,maxAuthenticationAttemptsAllowed=3],userName=captain.planet,deniedReasons=[]]
Workaround solution:
You can still enable the debug logging for the Default login manager package by adding the following line in the file log4j.properties:
- log4j.properties
log4j.category.com.atlassian.confluence.security.login.DefaultLoginManager=DEBUG
- log4j.properties: Confluence 7.13.2 or later
log4j.logger.com.atlassian.confluence.security.login.DefaultLoginManager=DEBUG
The following example trace will be added to the log file atlassian-confluence.log:
2020-06-15 10:16:29,032 DEBUG [http-nio-21310-exec-3] [confluence.security.login.DefaultLoginManager] onSuccessfulLoginAttempt Successful login attempt for user 'admin'
Attachments
Issue Links
- is cloned from
-
- Closed
-
- Closed