Lynxwork Azure DevOps OSLC Client - Installation and Usage Guide
Select the subsection that matches your Azure DevOps setup:
Installation
Install on Azure DevOps on-premises
HTTP Module for IIS
-
First, install HTTP Module for IIS by copying the provided file
AzureDevOpsSandboxModifier.dllto<AzureDevOpsInstallDir>\Application Tier\Web Services\bin. You can also add the provided*.pdbfile in the same directory, which will facilitate debugging.- Replace
<AzureDevOpsInstallDir>with the actual root folder where Azure DevOps Server is installed on your system (for example,C:\Program Files\Azure DevOps Server).

- Replace
-
Edit the
<AzureDevOpsInstallDir>\Application Tier\Web Services\web.configfile and add the following module registration, under<system.webServer><modules><add name="SandboxModificationModule"type="AzureDevOpsSandboxModifier.SandboxModificationModule, AzureDevOpsSandboxModifier"preCondition="managedHandler" />
-
Restart IIS
Upload and install the extension
-
Navigate to
https://your_devops_server_url/_gallery/manageand Click Upload extension
-
Select the provided extension file
MakeLynxworkAB.devops-oslc-client-app-1.0.xxx.vsixand upload it
-
Go to your main DevOps Server Collection home page

-
Click Collection Settings

-
Select Extensions

-
Select Browse local extensions

-
Select Lynx OSLC client extension

-
Select Get it free

-
Select the collection where you want to install it to

-
Click Install.
You are now done with the installation for Azure DevOps Server. It is now time to configure your extension.

Install on Azure DevOps Cloud
Lynxwork will first share the extension to your Azure DevOps Organization
-
Click at the Organization Settings

-
Under Extensions, select Shared

-
Select Lynxwork Azure DevOps OSLC Client

-
Click Install

-
Click makelynxwork

Configuration
Preview field
Now it is time to configure the extension. You first configure it at the organisation level, then you make project-specific configurations.
Navigate to your Azure DevOps main page and select Organization settings

-
Click Extensions

-
Click Azure DevOps

-
Click Process

-
Select the process you want to change. In this example makelynxwork Basic

-
Click Issue

-
Click Lynx item previews

-
Click New field

-
Click Text (multiple lines)

-
Select Add field

-
Click Hide from layout

-
Repeat the previous steps to configure all necessary work item types. Note that you can reuse the same custom field for all work item types.
License
Now it is time to configure the extension. Click on Lynxwork Azure DevOps OSLC Client (Global) and Active your license.
Friends
Now you are ready to connect Azure DevOps to external applications. Select Friends > Add Friend

-
Fill required fields then select Discover & Add.
For example, to become friends with Polarion, the Root Services URL has the form
https://polarion.your-organisation.com/polarion/oslc/rootservicesIf Polarion is the Friend, also apply Polarion 2512.

-
Select Save Changes

Relationships
Update the Relationships
The Relationships section defines link predicate that describe how resources are connected across different applications, such as Requirement oslc_rm:validatedBy TestCase. These predicates provide a shared, neutral vocabulary that enables both applications to understand and interpret the links between their resources in a consistent way.
The extension includes standard presets (example, Affects Requirement, Validates Requirement) marked with a Standard badge. You can use them as-is, customize them, or add your own by selecting Add Custom — providing a Label, Property URI, Inverse Property URI, and an optional Inverse Label. Changes are buffered until you select Save Changes.
Domains
Update the Domains
The Domains section manages namespace prefix definitions for CURIE (Compact URI) notation, turning long URIs into readable shorthand like oslc_cm:relatedChangeRequest. The extension ships with 9 standard prefixes covering core OSLC specs (oslc, oslc_cm, oslc_rm, oslc_qm, oslc_am, oslc_config, dcterms, rdf, rdfs). You can register additional namespaces via Add Custom by providing a Prefix and Namespace URI. Changes are buffered until you select Save Changes.
Type Mappings
Update the Type Mappings
The Type Mappings section define how your platform’s work item types (such as Bug or User Story) correspond to OSLC resource type URIs (for example, oslc_cm:Defect). This mapping ensures that work items are interpreted consistently when exchanged between applications.
The extenstion provides standard presets for common types. If your organization uses custom work item types, select Add Custom to define additional mappings. Changes are buffered until you select Save Changes.
Backlinks
Update Backlinks
The Backlinks section configures automatic creation of reciprocal links. When a work item is linked to an OSLC resource in a friend application, the extension automatically creates a corresponding backlink on the remote server that points back to the original item.
If you desire this functionality, enable Enable automatic backlink creation on and enter the base URL for the Azure DevOps OSLC Server (referred to in the Server instructions as {connector_base_url}).
Project configuration
You are done with the configuration at the organisation level. Now, it’s time to do project-specific configurations.

-
Go to your specific project.
-
Select Project settings

-
Click here.

-
Double-click the Selected OSLC Links field.

-
Click the Selection Dialog URL field.

Linking Configuration
Item Type
Authentication
-
On the Authentication step, select how the extension will connect to the OSLC Friend
- Basic Authentication — A simpler setup with a username and password (credentials are only saved in-memory)
- OAuth 1.0a — secure token-based authentication, tokens stored encrypted in your browser.
-
Select your preferred method, then select Next
-
Select a registered Friend from the dropdown.
- For Basic Auth, enter your Username and Password, then select Test Connection to verify — a success message shows the number of discovered providers.
- For OAuth, complete the authentication flow in the popup that appears,
- Select Discover Providers

Service Providers
After a successful connection, the wizard lists the discovered set of Friend projects (otherwise known as Service Providers.
External Type
The wizard now displays the OSLC selection dialogs available from the chosen provider.
-
Select Use dialog for the entry that matches the artifact type you want to link to (e.g., Requirements, Change Requests).
-
Select Next

Relationship Type
-
Choose the relationship that defines how links from your work items connect to the external resources. A Link flow summary appears at the bottom showing the full path: your work item, the relationship, and the destination resource type.
-
Select Next

Review
-
Select Launch selection dialog to test your configuration, as well as allow the extention to determine some suitable settings.
-
Review and fine-tune the settings such as Destination Resource Type.
-
Select Review.

Summary
The wizard now shows all your choices in one view
-
Review and select Apply Configuration to save the settings to your project.
-
You can click Back at any time to adjust a previous step.

Save your changes
-
Save your changes.

-
Repeat the above steps for every mapping of item types to types in the Friend application.
The extension configuration is complete. Now, it’s time to use this extension.
Usage Guide
Now, it’s time to use this extension. Open one of the issues under your project, by first selecting Boards
You can now see the Lynx Item Preview section. It’s position in the layout depends on the configuration choices you made earlier.
To create a link, select Add link…

-
Now the selection dialog from your external application appears. Search and select an item from the list.

-
Click this radio button.

-
Click Open DP-429

-
Click this icon.



