This is the documentation for Crucible 3.4. View the latest version of

Unknown macro: {spacejump}

or visit the latest Crucible documentation home page.

This page describes how to configure Trusted Applications for outgoing and/or incoming authentication for an application link.

Trusted Applications authentication allows one application to gain access to specified functions within another application on behalf of any user, without the user having to log in to the second application.

A typical scenario is to set up an application link between two applications which trust each other, have the same set of users and have the application links plugin installed. In this case, you would configure Trusted Applications for both outgoing and incoming authentication.

On this page:

  • Trusted applications are a potential security risk. When you configure Trusted Applications authentication, you are allowing one application to access another as any user. This allows all of the built-in security measures to be bypassed. Do not configure a trusted application unless you know that all code in the application you are trusting will behave itself at all times, and you are sure that the application will maintain the security of its private key.
  • Only use Trusted Applications authentication if both your servers have the same set of users and the servers fully trust each other.

  • The instructions below assume that both of the applications that you are linking have the Application Links plugin installed. If the remote application supports Trusted Applications but does not have the Application Links plugin installed, you will need to configure Trusted Applications from within the remote application (see the relevant administrator's documentation for the application) in addition to configuring the outgoing/incoming authentication for the application link as described below.
  • You must be a Crucible administrator to configure Trusted Applications authentication for an application link.

Configuring outgoing Trusted Applications authentication will allow the remote application to trust Crucible. In other words, Crucible will be able to access specified functions and data on the remote application.

To configure Trusted Applications authentication for an outgoing application link:

  1. Log in as a system administrator and go to the administration page. Click Application Links in the administration menu. You'll see a list of the application links that have already been set up.
  2. Click the 'Configure' link next to the application link that you want to configure Trusted Applications authentication for.
  3. Click the 'Outgoing Authentication' tab. The outgoing authentication page will show, with the 'Trusted Applications' tab displayed.
  4. If you are not currently logged into the remote application (or you logged into the remote application under a variant of the application's hostname, e.g. the IP address), a login dialog will display.
    • Enter the 'Username' and 'Password' for the remote server, (not your local server), and click the 'Login' button. You need to enter the credentials for the remote server, as the remote server needs to be instructed to trust your local server for the Trusted Applications protocol to work. If you are already logged into your remote server, then the appropriate changes can be made without having to log in again.
  5. Configure the settings for the Trusted Applications authentication:
    • 'IP Patterns' — Enter the IP addresses (IPv4 only) from which the remote application will accept requests (this effectively is the IP address your local server). You can specify wildcard matches by using an asterisk (*), e.g. '192.111.*.*' (note, you cannot use netmasks to specify network ranges). If you are entering multiple IP addresses, separate them with commas or spaces.
      (warning) Please note, if you are setting up Trusted Applications between two applications that both have the Application Links plugin installed, you can leave this field blank (or explicitly use *.*.*.*). However, if your remote application does not have the Application Links plugin installed and you are configuring the IP Patterns in the remote application (not the Application Links plugin), you must not leave this field blank nor use *.*.*.*. Failure to configure IP address restrictions in this scenario is a security vulnerability, allowing an unknown site to log into your site under a user's login ID.
      Consider the following scenarios, if you want to limit access by using this field:
      • If your local application is using a proxy server, you need to add the proxy server's IP address to this field.
      • If your local application is a clustered instance of Confluence, you need to configure the remote server to accept requests from each cluster node. If you do not set up each node appropriately, your Confluence users may not be able to view any information from the remote server. You can set this up by either specifying each individual IP address for each node of the cluster (e.g. 172.16.0.10, 172.16.0.11, 172.16.0.12), or specifying the IP address for the clustered Confluence instance using wildcards (e.g. 172.16.0.*).
    • 'URL Patterns' — Enter the URLs in the remote application that your local application will be allowed to access. Each URL corresponds to a particular application function. Enter one URL per line, as follows:
      • If your remote application is Jira, enter the following URL Patterns: /plugins/servlet/streams, /sr/jira.issueviews:searchrequest, /secure/RunPortlet, /rest, /rpc/soap
      • If your remote application is Confluence, enter the following URL Patterns: /plugins/servlet/streams, /plugins/servlet/applinks/whoami
    • 'Certificate Timeout (ms)' — Enter the certificate timeout. The default is 10 seconds. The certificate timeout is used to prevent replay attacks. For example, if a Trusted Applications request is intercepted and (maliciously) re-sent, the application will be able to check when the request was first sent. If the second request is sent more than 10 seconds (or whatever the certificate timeout is set to) after the initial request, it will be rejected. Please note, you should not have to change the default value of this field for most application links. Note that the certificate timeout relies on the clocks on both servers being synchronized.
  6. Click the 'Apply' button to save your changes.

Configuring incoming Trusted Applications authentication will allow Crucible to trust the remote application. The remote application will be able to access specified functions and data on Crucible.

To configure Trusted Applications authentication for an incoming application link:

  1. Log in as a system administrator and go to the administration page. Click Application Links in the administration menu. You'll see a list of the application links that have already been set up.
  2. Click Configure for the application link that you want to configure Trusted Applications authentication.
  3. Click the Incoming Authentication tab (the Trusted Applications tab will be displayed).

  4. Use the Modify or Configure buttons to configure Trusted Applications:

    IP Patterns

    IP addresses (IPv4 only) from which the local application will accept requests. Use commas or spaces to separate m

    Specify wildcard matches using an asterisk (*), e.g. 192.111.*.* (but you can't use netmasks to specify network ranges).


    (warning) If you are setting up Trusted Applications between two applications that both have the Application Links plugin installed, you can leave this field blank (or explicitly use *.*.*.*).

    However, if your remote application does not have the Application Links plugin installed and you are configuring the IP Patterns in the remote application (not the Application Links plugin), you must not leave this field blank nor use *.*.*.*. Failure to configure IP address restrictions in this scenario is a security vulnerability, allowing an unknown site to log into your site under a user's login ID.


    Consider the following scenarios, if you want to limit access by using this field:

    • If the remote application is using a proxy server, you need to add the proxy server's IP address to this field.
    • If the remote application is a clustered instance of Confluence, you need to accept requests from each cluster node, otherwise Confluence users may not be able to view any data from your application. Either specify the IP address for each node of the cluster (e.g. 172.16.0.10, 172.16.0.11, 172.16.0.12), or specify the IP address for your clustered Confluence instance using wildcards (e.g. 172.16.0.*).
    URL Patterns

    Enter the local application URLs that the remote application will be allowed to access – each URL corresponds to a particular application function.

    Enter one URL per line. as follows:

    /plugins/servlet/streams

    /sr/jira.issueviews:searchrequest

    /secure/RunPortlet

    /rest

    /rpc/soap

    /plugins/servlet/streams

    /plugins/servlet/applinks/whoami

    /rpc/xmlrpc

    Certificate Timeout (ms)

    Enter a certificate timeout value. The default is 10 seconds – you should not have to change this for most application links.

    The certificate timeout helps to prevent replay attacks. For example, if a Trusted Applications request is intercepted and (maliciously) re-sent more than the certificate timeout period after the initial request, it will be rejected. Note that the certificate timeout relies on the clocks on both servers being synchronized.

  5. Click Apply.

 

 

Configuring Basic HTTP Authentication for an Application Link
Configuring OAuth Authentication for an Application Link

  • No labels

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.