We designed ConductorOne to embrace the reality of today’s access environments—they can be complex and messy, and each one is unique. Many organizations are juggling a mix of cloud and on-prem apps and infrastructure, some of which are connected to IdPs, some of which are managed separately in the cloud, and some of which, like legacy or private apps, may be fully siloed from other systems.
Our goal is to meet teams where they are and help them secure access across their entire environment—whatever it looks like—by providing a flexible set of tools that extend our platform’s powerful access controls to any resource. Today we’re excited to announce the addition of webhooks to that toolset.
Now you can now configure webhooks to initiate provisioning workflows for any access approved through ConductorOne. This allows you to automatically activate provisioning for entitlements that aren’t set up to be directly provisioned through the platform. For example, if a service desk ticket needs to be created for manual provisioning, a webhook can be triggered to send information to the service desk that opens a ticket when access is approved. Access provisioning is just the start—we’ll be rolling out additional webhooks capabilities in the coming months to extend use cases across the platform.
How it works
To configure a webhook to provision access to an entitlement, simply add the webhook to ConductorOne and then set the entitlement’s Provisioning settings to use it.
When access to a webhooks-configured entitlement is approved, the approval event will trigger the selected webhook to deliver provisioning information to a designated destination.
How webhooks can be used to streamline provisioning
Create a service desk ticket for manual provisioning
As soon as access is approved in ConductorOne, a webhook can trigger creation of a ticket in Jira, ServiceNow, or any other service desk to immediately initiate a manual provisioning process.
Automatically provision access to resources that aren’t connected to ConductorOne
For resources like back-office portals, support dashboards, and private applications that aren’t provisioned directly through ConductorOne, a webhook can be configured to call the app’s API with approval information that triggers automatic provisioning.
Use pre-existing provisioning workflows outside of ConductorOne
If you already have provisioning workflows in place—for services like GitHub, for example—that you’d like to keep using, you can configure a webhook to trigger them automatically as soon as an approval event occurs in ConductorOne.
“ConductorOne’s new webhook functionality gives us greater flexibility in how we provision access. Using POST requests, we can provision access to repositories, initiate Slack notifications, or create a user when an application doesn’t have SCIM. This has really supercharged our configurability in C1.”
— Dmitrii Miroshnichenko, CIO, Revizto
Learn more about using webhooks in our docs.
More ways to integrate ConductorOne with your environment
In addition to webhooks, we provide a modern API, Terraform support, prebuilt and custom Baton connectors, and flexible deployment options that allow you to extend ConductorOne’s access controls across your environment. Visit our site to learn more about our developer-friendly toolset and custom connectors, or get in touch with our team for a demo!
