Talks to the systems you already run
ip·Solis connects your systems instead of replacing them. Bring your AD, your SCCM, your hypervisor and your IdP — ip·Solis ties them into one workflow.
Active Directory
The PowerShell 7 worker connects to AD over LDAP/LDAPS with NTLM message signing, so your existing domain credentials work without additional configuration. Runbook steps can add or remove users from security groups and query the directory. Manager relationships are resolved live at order-creation time for approval routing — never stored — so reporting-line changes are reflected immediately.
Entra ID (Microsoft Graph)
For cloud-only and hybrid estates, ip·Solis provisions Entra ID / Microsoft 365 group membership directly through the Microsoft Graph API using an app-only (client-credentials) registration — distinct from the OIDC login app. Grants and revokes are idempotent, so re-running an order is always safe. This closes the gap between OIDC login and actually provisioning cloud group access.
SCCM
SCCM integration is pure AdminService REST API over Kerberos — no agent, no WinRM. ip·Solis imports the device, assigns it to the OS (and application) collections, then polls task-sequence completion asynchronously and advances the order state on its own. The OS task sequence runs from collection membership. Works against both on-prem SCCM and Microsoft Endpoint Configuration Manager.
XenServer / XCP-ng
Drive VMs in a XenServer or XCP-ng pool from runbook steps via the XenAPI. Power and boot-order control ship as ready-made modules; clone, snapshot and delete are authored as your own XenAPI steps. SSL bypass for self-signed pool-master certificates is pre-configured, and stdin injection handles interactive-prompt workarounds so air-gapped lab environments work without script modifications.
VMware vSphere
For VMware estates, ip·Solis stores vCenter credentials in the admin UI and injects them per execution (never baked into scripts), and handles self-signed vCenter certificates. The VM-lifecycle actions — clone from template, configure hardware, power on/off, snapshots, delete — are authored as PowerCLI runbook steps that ip·Solis runs; no vSphere modules are bundled.
Generic webhook
The inbound ServiceNow webhook accepts HMAC-SHA256-signed payloads and routes them through the same approval and runbook pipeline as portal orders. Requester AD attributes are snapshotted at creation time, so webhook-originated orders appear correctly in cost-center and department breakdowns. The same pattern works for any HRIS or ITSM system that can POST a signed JSON payload.
SCIM 2.0 identity providers
The /scim/v2/ endpoint runs full joiner/mover/leaver provisioning with Okta, SailPoint, Ping Identity, Entra ID and any RFC 7644-compliant provider. A new user triggers assignment rules and orders the matched bundles; an attribute change reconciles entitlements; a deactivation (DELETE or PATCH active=false) revokes every active order and dispatches deprovision runbooks. A full SCIM filter grammar and a read-only /Groups shim are included.
Single sign-on (any OIDC IdP)
Portal sign-in works with any OpenID Connect provider via its discovery document — Entra ID, Okta, Ping, Google, Keycloak and others — with a login picker and RP-initiated logout. On-prem LDAP bind is supported alongside for environments without a cloud IdP.
SMTP
All outbound notifications — approval requests, reminders, expiry warnings, leaver confirmations, cost threshold alerts — are sent via your own SMTP server. STARTTLS on port 587 is supported. The from-address, from-name and credentials are configured in the admin UI and can be updated without rebuilding containers.
Microsoft Teams & Slack
Approval requests are delivered as Adaptive Cards to Microsoft Teams or as Block Kit messages to Slack — managers approve or decline with a single click via a signed link, without leaving the chat. Cost-threshold alerts post to Teams alongside email. Teams and Slack are independent channels; enable either or both.
Source-controlled runbooks
Runbooks can be exported as structured JSON and committed to a Git repository, enabling code review, diff history, and rollback through standard pull request workflows. The same JSON can be imported back into any ip·Solis instance, making runbook promotion across dev, staging, and production environments straightforward.