Skip to main content

​
Why are some connectors marked v2?

We’ve learned a lot since we started building connectors! One key advancement was the creation of the Baton framework for connector development, which C1 launched in December 2022. Since then, we’ve rolled out updated versions of some connectors that were written pre-Baton in order to modernize the connectors’ architecture, improve their performance, and enable new capabilities. (See the table below for an overview of new capabilities in v2 connectors.)

​
What happens to the v1 connector when a v2 is launched?

We want anyone setting up a connector for the first time to use the latest and greatest version, so when a v2 version is launched, we mark the original (v1) connector with a v2 available label on your Connectors page. This is intended primarily to lessen the chances that someone will set up a v1 connector by accident when a shiny new v2 version is available.

​
Are v1 connectors still safe to use?

Absolutely. We continue to support both versions of a connector so long as they’re in use. If we decide in the future to retire a v1 connector entirely, we’ll be in touch with anyone still using that connector well in advance of its retirement, and will provide support and guidance for migrating to the new version.

​
Migrate from a v1 to a v2 connector

Important: Migrating from a v1 to a v2 connector replaces internal identifiers. When you set up a v2 connector — whether in a new app or the same app as the v1 connector — C1 generates new app user IDs and entitlement IDs. Any existing tasks, access reviews, access review templates, or access profiles that reference the old v1 app’s users or entitlements will no longer resolve to the correct resources. Plan accordingly and review your tasks and access profiles after completing the migration.
The basic process for migration is as follows (see the special note below about migrating IdP connectors):
1
Leave the v1 connector running as-is.
2
Set up the v2 connector in a new C1 app. When you set up the v2 connector, select the Create a new managed app option.
3
Configure and test the v2 connector as needed.
4
When you’re confident the v2 connector is working as expected, remove the v1 connector and its associated app. Then update any access reviews, access review templates and access profiles that referenced the old app’s users or entitlements to point to the corresponding resources in the new v2 app.
This is a rip-and-replace process, not an in-place migration. Because you are creating a new app for the v2 connector, app user IDs and entitlement IDs will change. Any existing tasks or access profiles that reference IDs from the v1 app will break and need to be reconfigured for the new v2 app.
Depending on the complexity of the connected software and how you’ve set it up in C1, this process might be quite simple, or a bit more complex. Our Customer Success team is always ready to talk through the process with you and provide advice and support.
Thinking of migrating an IdP connector?If you’re ready to migrate to a v2 version of your identity provider (IdP) connector, make sure to talk with our support team before you proceed. Due to how IdP apps pull in child apps these connector migrations can have some special complexities, and we can help make sure the migration goes smoothly.

​
Version comparison

The table below outlines the differences between the v1 and v2 connectors, highlighting the key improvements in each newer version.