Feature: Add support for authenticating the Jamf collector with API client

[d3vzer0]

This PR adds two auth methods for the Jamf collector:

• Client/secret based authentication
• Username/password based authentication

This does introduce a breaking change. Previously the credentials were configured as follows:

[sources.source.jamf]
username = ...
password = ...
host = ...

This update requires the config (secrets.toml) to be set as:

# For user/password auth
[sources.source.jamf.credentials]
username = ...
password = ...
host = ...

# For client based auth
[sources.source.jamf.credentials]
client_id = ...
client_secret = ...
host = ...

Based on: #6

[Copilot]

Pull request overview

Adds a new authentication layer for the Jamf collector so it can authenticate either via username/password or via OAuth client credentials, and wires that into the DLT REST client used by the collector.

Changes:

• Introduces JamfPasswordCredentials and JamfClientCredentials plus a JamfAuth request auth handler.
• Updates the Jamf DLT source() signature to take a single credentials object and uses it to configure the REST client (base URL + auth).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/openhound_jamf/source.py	Switches the DLT source to accept unified credentials and uses JamfAuth for request authentication.
src/openhound_jamf/auth.py	Adds credential models for password/client auth and implements token acquisition + request header injection.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.