# Device42

## About <a href="#about" id="about"></a>

The Device42 context integration provides enriched asset context to Netography Fusion from the Device42 asset management platform. It connects to the Device42 API to retrieve asset information from the Devices table and then uploads it as [Context Labels](/enrich-traffic-with-context/labels.md) to the Netography Fusion API.

{% hint style="info" %}
**☁️NetoFuse Modules: Cloud deployment vs. on-prem deployment**

This page documents how to add and configure the context integration in the Netography Fusion Portal. This will make a direct connection from the Netography Fusion SaaS in the cloud to the vendor API. If you prefer to deploy the integration within your own environment (on-prem or in your own cloud) with a container or Python package, go to the module documentation in [NetoFuse Modules](broken://pages/6i3otB8UAClHx08Umd0Y).
{% endhint %}

## Adding a Context Integration <a href="#adding-a-context-integration" id="adding-a-context-integration"></a>

In the Netography Fusion Portal:

1. Select **Settings** at the bottom of the left-hand navigation menu
2. Select **Context Integrations** in the **Data Management** section.
3. Select the **Add Integration** button.
4. Select a context integration from the list provided.
5. Follow the configuration steps in the documentation for the context integration you selected.

## Configuring <a href="#configuring" id="configuring"></a>

| Field         | Required | Description                                                                    |
| ------------- | -------- | ------------------------------------------------------------------------------ |
| URL           | Yes      | URL to Device42 API                                                            |
| Username      | Yes      | Device42 User Authentication Username, if used instead of Token Authentication |
| Password      | Yes      | Device42 User Authentication Password, if used instead of Token Authentication |
| IP Fields     | Yes      | Device42 fields to retrieve via API                                            |
| Fetch Devices | No       | If set to true, gathers additional fields from Devices table in Device42       |
| Per Page      | No       | Number of results per API call (max: 1000)                                     |

### Selecting Token Authentication or User Authentication <a href="#selecting-token-authentication-or-user-authentication" id="selecting-token-authentication-or-user-authentication"></a>

*Token authentication is being added in an upcoming release. If you would like to use token authentication now, please contact Netography Support.*

Device42 can use either Token Authentication or User Authentication to connect to the API. Token authentication is the recommended approach for a production deployment.

The `Username` and `Password` fields are not required if token authentication is used (and conversely, the `Client Key` and `Client Secret` fields are not required if User authentication is used).

## Device42 Configuration <a href="#device42-configuration" id="device42-configuration"></a>

If using Token Authentication, follow Device42 instructions to generate a `Client Key` and `Client Secret` for a production deployment as documented here: <https://api.device42.com/#API_Authentication>

### Transform <a href="#transform" id="transform"></a>

The **Advanced** section of the context integration contains the *Transform* field. This field allows you to add, remove, or change the mapping of fields returned by the vendor API to Netography Fusion context labels.

See the [Context Transforms](/netofuse/context-transforms.md) documentation section for more instructions on editing this field.

It may be helpful to first configure all the parameters and the transform field with a [NetoFuse](/netofuse/about.md) container on your local system and then copy those fields into the Portal once you have validated that everything is configured properly.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fusion.vectra.ai/enrich-traffic-with-context/configure-context-integrations/device42-context.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.