Configure Connection
PaperCut guide
Prepare PaperCut API access, enter the hostname and authentication token in NIM, and collect users to verify the connection.
Before you startDirect link to Before you start
Prepare a service account for the integration and configure API access following the PaperCut Web Services API security documentation. NIM requires Hostname and Authtoken; the connection uses an API authentication token.
Verify access by collecting data
The connector currently always returns success for Test Connection. This result does not verify connectivity or credentials. Run a collection from the system to test the connection.
Configure PaperCut Web Services accessDirect link to Configure PaperCut Web Services access
- Arrange the integration service account with your PaperCut administrator.
- In PaperCut, go to Options > Advanced > Allowed XML Web Services callers and allow the IP address of the NIM server making the API calls.
- Open Options, select Config editor (advanced) from the Actions menu, and find
auth.webservices.auth-token. - Configure a dedicated token for NIM using a supported format from the vendor documentation, preserve any tokens used by other integrations, and apply the change with Update.
- Record the PaperCut server hostname and NIM's token value.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add a PaperCut system, or select the existing system.
- Open its Connection screen.
- Enter the following settings and save the connection.
| NIM setting | Value |
|---|---|
| Hostname | The hostname of the PaperCut server NIM will connect to. |
| Authtoken | The authentication token configured for NIM in PaperCut. Enter the token value, rather than the entire token configuration. |
Test access by collecting usersDirect link to Test access by collecting users
- Run a collection from the PaperCut system in NIM. Test Connection currently always returns success and cannot be used to verify access.
- Confirm that collection completes successfully and inspect the Users data.
- If collection fails, check the hostname, network access from NIM, token value, and PaperCut's allowed XML Web Services callers.
- Validate a supported user update with a safe test record before enabling scheduled lifecycle automation.
Successful collection verifies read access. Validate the intended user updates separately.
Step 1 of 3