Qintorava DocsProduct documentation
Integration profile

Deployment integration · Microsoft Configuration Manager · API adapter

Connect an approved deployment adapter implementing the Qintorava bundle/target/package API contract. The adapter is responsible for native provider execution and must return a real execution ID and status.

Demo baseline · November 13, 2026
Download PDF

Prerequisites

  • Customer-approved HTTPS deployment adapter
  • Protected read-only test API
  • Secret Manager adapter credential
  • Native provider configuration and permissions managed by the adapter

Configuration steps

  1. Configure adapter endpoint and authentication
  2. Test authenticated API access
  3. Approve a bundle request
  4. Dispatch and refresh the returned provider execution

Provider fields

FieldTypeRequirement and options
Adapter base URL
baseUrl		urlRequired
Adapter authentication
authScheme		selectRequired
bearer_token, api_key, basic, oauth2_client_credentials
Protected API test path
testPath		textRequired
Deployment request path
deploymentPath		textRequired
Execution status path with {id}
statusPath		textRequired
API-key header name
apiKeyHeader		textOptional
OAuth token URL
tokenUrl		urlOptional
OAuth scopes
scope		textOptional

Verify and troubleshoot

Test with the narrowest supported non-production scope. Confirm that the connection test reaches the expected provider and that the preview or receipt matches the intended scope. Check identity, credential references, network access and provider permissions before retrying. Record the failure stage and redact sensitive payloads when escalating.