Skip to end of banner
Go to start of banner

WIP: Configuration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The configuration settings affect the way certain parameters of the app's macros work, in general.

After installing HTML for Confluence, navigate to the HTML for Confluence Configuration screen:

  1. Log in with the System Administrator global permission.
  2. Select  > Manage apps.
  3. Either search for HTML for Confluence or scroll to Bob Swift Configuration, and click HTML to view app configuration.

Try this for older Confluence versions!

  1. Navigate to  > Settings > Atlassian Marketplace on the sidebar.
  2. Scroll to Bob Swift Configuration and click HTML to view the configuration page.

The following configuration tabs are available:

Global configuration

Use the toggles to enable or disable the Global Configuration settings.

ParameterDescription
Default output type

Specify the output format for the Visio diagram. The options are as follows:

  • default - Display output in the format that has been chosen as the default for this Confluence instance.
  • best - Display output in the best format applicable for the system and browser used. This means using the Visio control on Internet Explorer (IE) or IE tab capable browsers and a converted image (if available) otherwise.
  • visio - Display using the IE Visio control. This requires IE or IE tab capable browser on Windows.
  • svg - Display as a SVG image converted from the Visio diagram. Only available if conversion support has been enabled on your Confluence installation.
Restrict URL access

Enable this option to restrict access to remote locations through the URL to Visio file parameter in the Visio macro. The specified URLs in the macro editors must conform to the Confluence Whitelist; provided, whitelisting is enabled.

Confluence allows the administrator to turn on whitelisting to restrict incoming and outgoing connections to only those connections that are configured in the Whitelist settings. If enabled, the URL to Visio file parameter for the Visio macro is also restricted to only URLs that are configured in the Whitelist settings for Confluence.

Blacklist domains

Enable this option to blacklist certain domains. By default, this option is disabled for backward compatibility.

If enabled, and if a request from any of these sites is received, an error message is displayed. However, if users still need to access a blacklisted site, they must contact their administrator to disable this option.

If this option is disabled, access to all domains is permitted!

Click the link named listed (in the description beneath the option) to view a pre-defined list of the most commonly blacklisted domains in a pop-up window. The following sites are blacklisted:

  • 10.0.0.0/8
  • 100.64.0.0/10
  • 127.0.0.0/8
  • 169.254.0.0/16
  • 172.16.0.0/12
  • 192.168.0.0/16
  • 192.0.0.0/24
  • 198.18.0.0/15
  • 255.255.255.255/32
  • 0.0.0.0/32
  • 192.88.99.0/24
  • 198.51.100.0/24
  • 203.0.113.0/24
  • 224.0.0.0/4
  • 240.0.0.0/4
Help Us Improve the ProductEnable this option to allows us to collect some usage data that helps us improve our product. To learn more about what is being sent, refer to Analytics data.

Profiles

Profiles are a common set of parameters used to access content from external locations. Available since 5.3.0. 

Use profiles to:

  • Allow user authentication as required by some URLs to be hidden from page viewers and editors. Only Confluence administrators have access to this information.
  • Enable macro editors to quickly configure the macro by reusing a shared definition for URL access. 
  • Make lesser changes to page contents when base URLs are relocated as relative addressing is used in profiles. 
  • Macro configured URL (that is not a full URL) is appended to the profile provided URL. This absolute URL then points to the actual location of the content to be rendered.

    The base URL of the remote location to be accessed must be given in profiles, and the raw URL must be entered in the URL to the Visio file field in the macro editor. 

    A raw URL is defined as the part of the URL following the domain information and includes the query string, if present. For example, in the URL string http://www.contoso.com/articles/recent.aspx, the raw URL is /articles/recent.aspx.

The page displays a list of profiles available for the macros. You can perform the following actions on this page:

  • Click  to edit the profile details.
  • Click  to remove the profile.

To create a new profile, click Add Profile to open a pop-up window as:

ParameterDescription
Profile name

Enter a name for the profile. Profile names given here are populated in the Profile field in the macro editor.

This name must be unique; else, the details specified overwrites the details of the existing profile. This may cause errors in pages where the profile is used.

Profile type

The default option for this parameter is URL

Currently, only URLs are supported for use in profiles. In the upcoming releases, the support will be extended to access Visio files in other applications such as GitLab and GitHub.

URL

Enter the URL of the remote location to be accessed. It is recommended to provide the base URL here. 

A raw URL must be provided in URL to the Visio file in the respective macros' editors.

User; Password

Enter the username and password, if required, to access the specified URL. 

Specify either the User and Password parameters or the Access token, as an access token is also a means of user authentication. It is recommended to use either of the user authentication methods but not both.

Access token

Enter an access token or an API token for the application or service to be connected with. 

If this parameter is specified, ensure that the User and Password parameters are left empty. It is recommended to use either of the user authentication methods but not both.

Each application has its own method of generating tokens. Access tokens or API tokens are a means of user authentication; so, if mentioned, this token is used for authentication instead of using user credentials.

  • Tokens are generated for a user after the application or service to be connected verifies the user's credentials. 
  • Enter the generated token here for a seamless connection between the app's macros and the application or service.

For example, refer to this article to generate a personal access token for Bitbucket.

URL parametersMention any extra parameters (for the query string) that must be appended to the specified URL here. 
Request headersDisplays the request headers created as per the given information. Request headers are name or value pairs that are added to the request. For example, GitHub requires the following request headers be specified: Authorization: token $accessToken, Accept:application/vnd.github.v3.raw

This field is automatically populated with a comma-separated list of name or value pairs using the provided information. If required, enter additional name or value pairs separated with commas.

Click Save profile to create the profile.

  • No labels