Documentation for Crucible 3.0.x. Documentation for other versions is available too.

This page describes how to add a new application link in Crucible. The process for adding an application link depends on whether or not the application you are linking Crucible to supports Atlassian's Application Links.

If you are linking Crucible to an application that does not have Application Links, you will need to do additional configuration in that application. This is because Application Links in Crucible will not be able to automatically configure authentication in your remote application.

On this page:

Check the following settings. This is required for synchronisation to work correctly:

To link to an application that supports Application Links:

  1. Log in as a system administrator and go to the administration page. Click 'Application Links' in the administration menu. The 'Configure Application Links' page will appear, showing the application links that have been set up.
  2. Click 'Add Application Link'. Step 1 of the link wizard will appear.
  3. Enter the server URL of the application that you want to link to (the 'remote application').
  4. Click the 'Next' button. Step 2 of the link wizard will appear.
  5. Enter the following information:
    • 'Create a link back to this server' – Tick this check box if you want to create a two-way link between the remote application and your application. If you want to do this, you will need to enter the username and password of an administrator for the remote application.
      Note: These credentials are only used to authenticate you to the remote applicaiton, so that Application Links can make the changes required for the new link. The credentials are not saved.
    • 'Reciprocal Link URL' – The URL you give here will override the base URL specified in your remote application's administration console, for the purposes of the application links connection. Application Links will use this URL to access the remote application.
  6. Click the 'Next' button. Step 3 of the link wizard will appear.
  7. Enter the information required to configure authentication for your application link:
    • 'The servers have the same set of users' or 'The servers have different sets of users' – Select one of these options depending on how you manage users between the two applications.
    • 'These servers fully trust each other' – Tick this check box if you know that the code in both applications will behave itself at all times and are sure each application will maintain the security of its private key.
      For more information about configuring authentication, see Configuring Authentication for an Application Link.
  8. Click the 'Create' button to create the application link.

Screenshots: Adding an application link to an application that supports Application Links (click to view full-sized images)

Step 1
Step 2
Step 3

 

To link to an application that does not support Application Links:

  1. Log in as a system administrator and go to the administration page. Click 'Application Links' in the administration menu. The 'Configure Application Links' page will appear, showing the application links that have been set up.
  2. Click 'Add Application Link'. Step 1 of the 'Link to another server' dialogue will be displayed.
  3. Enter the server URL of the application that you want to link to, in the 'Server URL' field. Click the 'Next' button. Step 2 of the 'Link to another server' dialogue will be displayed.
  4. Fill out the fields, as follows:
    • 'Application Name' — Enter the name by which this remote application will be referred to, in your application.
    • 'Application Type' — Select the type of application that you are linking to: Generic, FishEye/Crucible, Confluence, Stash, Bamboo, JIRA.
    • 'Application URL' — This will be set to the server URL you entered in the previous step and will not be editable.
  5. Click the 'Create' button to create the application link. The 'Configure Application Links' page will be displayed, listing all of the application links that have currently been set up for your application including the one you just added.
  6. Configure the desired authentication type (Trusted Applications, OAuth, basic HTTP, none) for your new application link. See Configuring Authentication for an Application Link.
  7. In your application that does not support Application Links, configure the same type of authentication that you configured for your application link's outgoing authentication (in the previous step). For example, if you configured outgoing Trusted Applications authentication in your Application-Links-enabled application, you also need log into your non-Application-Links application and manually configure Trusted Applications (see the relevant administrator's documentation for the application).

Screenshots: Adding an application link to an application that does not support Application Links (click to view full-sized images)

Step 1
Step 2

 

Making an application link the primary link
Configuring authentication for an Application Link
Configuring project links across applications

  • No labels

 

 

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