Security Settings

Learn how to access and define Security Settings in Golive.

In this article, you'll learn how to access and configure Golive's security settings.

Security Settings provide Jira administrators with centralized controls for security-sensitive Golive features.

Security Settings Page

The Security Settings page is the central place for managing security-related controls in Golive.

Requirements

To access and manage the Security Settings page, you must be a Jira Administrator.

The Golive Administrator permission alone does not provide access to these settings.

Accessing the Security Settings Page

1. Click the gear icon located in the upper-right corner of any Golive Page.

2. From the drop-down menu, select Golive Settings.

3. In the Settings section, select Security Settings.

This will open the Security Settings page.

Golive Automations

The Golive Automations setting controls whether Golive Automation rules are available and can run across Golive.

Click Edit and select one of the following options:

Enabled

When Golive Automations are enabled:

• The Golive Automations section is available.

• Existing automation rules can run.

• Authorized users can create and manage automation rules.

• Rules can send outbound requests to configured services and endpoints.

Disabled

When Golive Automations are disabled:

• The Golive Automations section is hidden.

• Existing rules are preserved but cannot run.

• No new rules can be created or configured.

• No outbound requests can be executed by Golive Automations.

This includes requests to services such as Slack, Microsoft Teams, and custom endpoints.

Re-enabling Golive Automations restores access to the existing rules. Disabling the feature does not delete them.

XSS Sanitization

The XSS Sanitization setting controls how Golive validates and sanitizes content entered in HTML-based fields, including attribute values.

Click Edit and select one of the following modes:

Validation

Users cannot save invalid content and must correct it before continuing.

Previously stored invalid content is displayed without being automatically sanitized.

Explicit Sanitization

Users cannot save invalid content and must correct it before continuing.

Previously stored invalid content is sanitized whenever it is displayed.

Silent Sanitization

Invalid content is automatically sanitized when users save or display it. Users are not notified that the content has been modified.

Disabled

XSS sanitization is completely disabled.

For more information on Cross-Site Scripting (XSS), visit the OWASP website.

Jira Allowlist for Golive Automations

The Jira Allowlist for Golive Automations setting controls whether Jira's URL validation rules are applied to URLs configured in Golive Automations.

Click Edit and select one of the following options:

Enabled

Golive uses Jira's URL validator before executing outbound requests.

Requests to URLs rejected by Jira are blocked.

Refer to Atlassian's documentation about configuring the Jira allowlist

Disabled

Golive does not use Jira's URL validator for outbound requests sent by Golive Automations.