Comments
-
To exclude the okta spam in the log files: Stop the application Go to: /atlassian/jira/atlassian-jira/WEB-INF/classes edit: log4j.properties add: # reduce okta logs log4j.logger.com.atlassian.jira.authenticator.okta = ERROR, console, filelog Start the application
-
cleared my cache, everything is working fine now.
-
I have the issue only in chrome Version 89.0.4389.128 (Official Build) (64-bit) In Edge it is working fine:
-
-
Until some months ago I was a solo/ full time Atlassian admin. Since march I have a new colleague. To me this was needed for the continuity (during holidays) and it helps to have an other view on a possible solution. He is doing the more technical issues (incidents / bugs) and I'm doing the more functional issues + talking…
-
somebody has an idea on the okta package name for Confluence? Will it be that simple to replace jira with confluence? log4j.logger.com.atlassian.jira.authenticator.okta = ERROR, console, filelog
-
No answers? :s
-
edited wrong account