wifimop.blogg.se - Atlassian confluence versions

ATLASSIAN CONFLUENCE VERSIONS HOW TO
ATLASSIAN CONFLUENCE VERSIONS INSTALL
ATLASSIAN CONFLUENCE VERSIONS PASSWORD

ATLASSIAN CONFLUENCE VERSIONS INSTALL

Logs are written to the install directory, and you may want to monitor these logs using your preferred monitoring tool. Learn about the confluence-administrators super groupĪvoid shared admin accounts, and easily guessed usernames like 'admin' or 'jdoe'. Consider providing administrators with two accounts, allowing them to use different accounts for day-to-day Confluence use and administrator tasks.Īccess logs can help you identify unusual activity. Consider limiting the members of this group and instead create a new group with system administrator global permissions. Members of this 'super group' can access all admin functions and access all content, including restricted pages.

Review confluence-administrators group membership.

ATLASSIAN CONFLUENCE VERSIONS HOW TO

Learn how to manage personal access tokens Provide a more secure way to authenticate API requests than basic authentication (username and password) Use personal access tokens for integrations.Limit incoming and outgoing connections to avoid Server-Side Request Forgery (SSRF) attacks. Learn how to turn on secure administrator sessions

ATLASSIAN CONFLUENCE VERSIONS PASSWORD

Require admins to re-enter their password to access admin functions, and set a short timeout for the administrator session. Limit database access to just the Confluence host (using iptables or built in database security tools). Refer to your database documentation to find out how to do this. Limit the hosts that can mount NFS file systems to just the Confluence host (such as in the /etc/exports file in Linux). Refer to your operating system documentation to find out how to do this.

Limit hosts which can mount network file systems.

Learn how to allow the account to write to particular directories

Limit the accounts that can access Confluence directoriesĮnsure only selected user accounts can read and write to Confluence directories, including custom directories where you might store attachments, backups, or data pipeline exports.

Learn how to create a dedicated user account Limit that account to just the directories that Confluence needs to write to.

Run Confluence with a dedicated non-root user account.

Receive security advisory alerts and other important technical updates.

Subscribe to advisory alerts and keep technical contact details up to date.

We've put together a list of things you might want to check as part of this upgrade, as our recommendations may have changed since you first installed Confluence. Upgrading to a new Long Term Support release is a great time to check your site security. So what can you expect from Confluence 7.13? We've been focused on raising the already high bar we’ve set for quality, stability, and performance, and have tackled some particularly high impact bugs to make sure Confluence 7.13 is the best it can be.

Analytics for tracking page views, edits, and more.Īll in all we've resolved over 260 issues since 7.4.0 For a bird's eye view of all the changes, check out the Confluence 7.13 Long Term Support Release Change Log.

Webhooks and personal access tokens for better integrations.

More audit log events, including logging end-user activity.

In that time we've shipped a huge amount of value, especially for Data Center: It's been more than 12 months since our last long term support release, Confluence 7.4. Ready to upgrade? Check the 7.13 LTS change log for a roll-up of changes since 7.4. This means we'll provide bug fix releases until 7.13 reaches end of life, to address critical security, stability, data integrity, and performance issues. Since the last Long Term Support release.Ĭonfluence Server and Data Center 7.13 is a Long Term Support release