Securing Jira applications with Apache HTTP Server
System administration
- Finding your Server ID
- Increasing Jira application memory
- Using the database integrity checker
- Precompiling JSP pages
- Logging and profiling
- Backing up data
- Restoring data
- Search indexing
- Using robots.txt to hide from search engines
- Control anonymous user access
- Moderating user group activity with Safeguards
- Licensing your Jira applications
- Viewing your system information
- Monitor application performance
- Monitoring database connection usage
- Monitor your instance with Jira diagnostics plugin
- Viewing Jira application instrumentation statistics
- Generating a thread dump
- Finding your Jira application Support Entitlement Number (SEN)
- Auditing in Jira
- Monitor security threats
- Data pipeline
- Important directories and files
- Integrating Jira applications with a Web server
- Securing Jira applications with Apache HTTP Server
- Changing Jira application TCP ports
- Connecting to SSL services
- Running Jira applications over SSL or HTTPS
- Configuring security in the external environment
- Data collection policy
- Jira Admin Helper
- Raising support requests as an administrator
- Start and Stop Jira applications
- Managing LexoRank
- Jira cluster monitoring
- Scheduler administration
On this page
In this section
Related content
- No related content found
The following outlines some basic techniques to secure a Jira instance using Apache HTTP Server. These instructions are basic to-do lists and should not be considered comprehensive. For more advanced security topics see the "Further Information" section below.
- Using Apache to limit access to the Jira administration interface
- Using Fail2Ban to limit login attempts (Jira 4.1 has login-rate limiting, but Fail2Ban can be useful for older versions and more advanced security setups.)
Further information
Last modified on May 11, 2018
In this section
Related content
- No related content found
Powered by Confluence and Scroll Viewport.