Question
As part of the recent company acquisition of Idaptive by Idira in May 2020, Idira is planning to decommission the cloud tenant domain of
centrify.com and will require all customer configurations to use the domain suffix idaptive.app.
Idira is extending the previous December 15th, 2020 expiration date for our customers until February 28th, 2021 to allow additional time for updating the default tenant URL, applications, and endpoints to use an Idaptive URL suffix of idaptive.app. This is to prevent any service disruptions for our customers.A new feature is available starting with CyberArk-Idaptive version 21.1 that will allow administrators to disable forwarding from all *.centrify.com to Idaptive domains before February 28th. The purpose of this feature is to temporarily disable domain forwarding to identify applications that still use the legacy domain in their configurations. For more information, please see Idira article KB-9766: How to disable URL forwarding for an Idaptive cloud tenant This article applies only to cloud tenants migrated from Centrify to Idaptive pods that would likely include *.
centrify.com configurations. This does not apply to cloud tenants created directly on Idaptive cloud pods and were not migrated from Centrify. If unsure your tenant was migrated to Idaptive, please contact Idaptive Support.
Idaptive is providing this FAQ so customers can start with the URL transition at any time without impact to production systems. For most tenant configurations, updating Service Provider (SP) application settings will have the highest priority and we encourage administrators to get started with these updates right away.
Answer
Frequently Asked Questions1. How will the tenant URL change?2. Why is Idaptive transitioning to idaptive.app and not cyberark.com?3. What is the final date for the transition?4. Will there be any impact to end-users?5. Will current applications require any updates?6. Are any actions required for Endpoints - Mac, Windows, or mobile?7. Are any actions required for the Connector?8. Will there be any impact to MFA?9. Are any actions required for Idaptive API's?10. Is there any impact on Idaptive plug-ins?11. Are any actions required for Directory Services (B2B Federation, Google Directory Service)?12. What if I encounter issues during the transition and need assistance?1. How will the tenant URL change?Cloud Tenants will change to a URL suffix of idaptive.app. Idaptive plans to update all tenants to use a default Idaptive URL suffix during our 20.3 release, currently targeted for release end of August 2020. If a tenant is using a default URL of company.my.centify.com, the new preferred URL will be automatically updated to company.my.idaptive.app. The tenant URL suffix will change but customers can continue to use a company or custom URL prefix just as before. Changes to the default URL does not impact tenant functions, applications (including Office 365), or custom company URLs.
Administrators are recommended to update the preferred tenant URL to use *.idaptive.app before the 20.3 release. Idaptive has included an application report to display apps that may be using the
centrify.com suffix but the default tenant URL must be changed to *.
idaptive.app first before running the report with accurate results.
Idaptive has published article
KB-8616: How to update the default Tenant URL to use idaptive.app that includes a brief quick Video with the easy steps to change the tenant URL.
2. Why is Idaptive transitioning to idaptive.app and not cyberark.com?As part of the recent company acquisition of Idaptive by Idira in May 2020, Idaptive is required to discontinue the use of the cloud tenant domain
centrify.com and will transition all customers to use
idaptive.app by February 28th, 2021. Idira is now the legal owner of the idaptive.app domain but there are no plans to transition this branding to Idira domain naming. This is consistent with other Idira product offerings.
3. What is the final date for the transition?Idaptive is planning to transition all cloud tenants to use a default tenant URL with idaptive.app during our 20.3 release, currently targeted for the end of August 2020 but will retain DNS for the
centrify.com CNAME until
February 28th, 2021. This should allow time for customers to update application metadata with service providers, endpoint enrollments, and API configurations.
4. Will there be any impact on end-users?Administrators should communicate the URL change and device requirements to end-users to prevent future login issues after the legacy domain is removed in February 2021. Once the default tenant URL is updated, users should use and will see the new idaptive.app suffix in the browser address bar. All users, applications, or endpoints that continue to authenticate using
centrify.com after the default tenant URL change will still function and are automatically directed to the Idaptive URL but only until
February 28th, 2021, so user notification is important.
5. Will current applications require any updates?Administrators must update all apps and SAML metadata with Service Providers (SP) to use Idaptive URLs. For more information, please see Idaptive article
KB-8625: How to update application metadata to use an Idaptive URL suffix of idaptive.app or refer to our
online documentation for configuring SAML SSO.
Administrators can log in to the Admin Portal and run the built-in application report named “Apps using Centrify Url” to retrieve a list of applications and app types that will need to be updated. Idaptive recommends running the report with a date range of 90 days to ensure infrequently used apps are not skipped The application URL updates are generally performed within the app Service Provider’s (SP) administration portal where SAML metadata URLs should be updated from using *.
centrify.com to *.idaptive.app. Customers are encouraged to work with application owners and service providers early in case extra time is required for these changes.
Note for Customers that use Office 365. If the Office 365 app appears in the
Centrify.com URL report, Administrators will need to navigate to the Office 365 app settings within the Admin Portal and Re-Federate all domains configured for use with Idaptive per article
KB-8625: How to update application metadata to use an Idaptive URL suffix of idaptive.app . This will update your federation URLs and should be silent for users.
6. Are any actions required for Endpoints - Mac, Windows, or mobile?Android and iOS endpoints that are used for SSO only and do not use the Idaptive Identity platform for mobile device management should not require any actions. This is managed by the Admin Portal device policy
Endpoint Policies > Device Management Settings > Use the Idaptive Identity platform for mobile device management (default = Yes).
Android, iOS, Mac, and Windows endpoints enrolled for MDM will require different actions. For detailed information, please see Idaptive article
KB-8629: How to update endpoints to use an Idaptive URL suffix of idaptive.app . The KB article includes instructions for creating an administrator report of devices that require actions before
February 28th, 2021.
Device Actions Summary:Android devices should update to the 20.3 Idaptive mobile app when released. After installing the 20.3 mobile app, no additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic.
iOS devices must unenroll and re-enroll with the cloud service before
February 28th, 2021. When a device is re-enrolled using the Idaptive mobile app, it is important to verify the app settings are using a login URL of
https://pod0.idaptive.app. After enrollment is complete, no additional actions are needed when the legacy URL is removed.
Mac computers that are enrolled using the Idaptive Mac Cloud Agent (MCA) should re-enroll with the cloud service before
February 28th, 2021. After the Mac is re-enrolled, it is important to verify the MCA setting is using a login URL of
https://pod0.idaptive.app. No additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic. Mac computers that were joined to Active Directory using the DirectControl agent and simultaneously enrolled with the cloud should unenroll and re-enroll using the Idaptive app. Note that users will need admin rights to perform enrollment.
Windows computers that are enrolled using the Idaptive Windows Cloud Agent (WCA) should update to the 20.4 WCA agent when released. After installing the 20.4 agent, no additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic. Windows computers that were enrolled to the Idaptive Cloud using Microsoft's built-in device management client https://docs.idaptive.com/Content/Endpoints/EnrollEndpoints.htm should unenroll and re-enroll using a server URL of pod0.idaptive.app.
NOTE: Idaptive strongly recommends administrators to update and maintain Mac and Windows cloud agents, Idaptive Browser Extension (IBE), and the Idaptive mobile device app with the latest released versions. Keeping components up to date will ensure users receive the latest improvements and updates.
7. Are any actions required for the Connector?A new connector feature will be included in 20.3 that will automatically manage the tenant URL change silently in the host registry. If administrators simply update to 20.3 connectors when released, no additional changes are required. If the installation of 20.3 is not possible, administrators must re-register all connectors using a hostname of pod0.idaptive.app. Connector versions below 20.3 that do not re-register will be unable to communicate with the cloud service once *.
centrify.com is retired on
February 28th, 2021.
8. Will there be any impact to MFA?Customers that use FIDO2 or on-device authenticators require login to a specific tenant URL. It is recommended for customers to re-register these devices using the preferred URL of *.
idaptive.app after changing from *.
centrify.com.
Additionally, if you are using the ADFS plugin, admins must re-register the plugin by modifying the IdaptiveConfig.json to use the idaptive.app url and then restart the ADFS service.
9. Are any actions required for Idaptive API's?Administrators can run a report named "APIs using Centrify Url" to display a list of APIs using Centrify URLs within a specific date range. Customers should update any API configurations to use idaptive.app by
February 28th, 2021 to prevent any loss of functionality. For additional information, please refer to our
API online documentation.
10. Is there any impact on Idaptive plug-ins such as ADFS, Confluence, or Jira?Customers using Idaptive plugins for ADFS, AWS CLI, Bitbucket Server, Confluence Server, Jira Server, ServiceNow, and SharePoint Server SAML should refer to
Idaptive online documentation for specific SSO application configuration steps.
11. Are any actions required for Directory Services (B2B Federation, Google Directory Service)?Google Directory Service (GDS) by default will not require a change, but if you have a custom Whitelist in your GDS tenant you will need to update the Whitelist to include your new *.my.idaptive.app URL.
B2B Federations whether using SAML or WS-Fed protocol must update their metadata on both Idaptive and IDP side to use the *.idaptive.app URLs.
12. What if I encounter issues during the transition and need assistance?If you encounter any issues or have questions related to updating applications or other tenant settings, Idaptive Support is the primary place to request assistance. Please log a case via our portal at
https://community.cyberark.com/s/ or call our support line at 408-495-8118 for urgent assistance.
Sometimes, the best way to solve a problem is to grant Idaptive support read-only access to your tenant so engineers can review your tenant configuration. For more information, please refer to Idaptive online documentation.
As part of the recent company acquisition of Idaptive by Idira in May 2020, Idira is planning to decommission the cloud tenant domain of centrify.com and will require all customer configurations to use the domain suffix idaptive.app.
Idira is extending the previous December 15th, 2020 expiration date for our customers until February 28th, 2021 to allow additional time for updating the default tenant URL, applications, and endpoints to use an Idaptive URL suffix of idaptive.app. This is to prevent any service disruptions for our customers.
A new feature is available starting with CyberArk-Idaptive version 21.1 that will allow administrators to disable forwarding from all *.centrify.com to Idaptive domains before February 28th. The purpose of this feature is to temporarily disable domain forwarding to identify applications that still use the legacy domain in their configurations. For more information, please see Idira article KB-9766: How to disable URL forwarding for an Idaptive cloud tenant
This article applies only to cloud tenants migrated from Centrify to Idaptive pods that would likely include *.centrify.com configurations. This does not apply to cloud tenants created directly on Idaptive cloud pods and were not migrated from Centrify. If unsure your tenant was migrated to Idaptive, please contact Idaptive Support.
Idaptive is providing this FAQ so customers can start with the URL transition at any time without impact to production systems. For most tenant configurations, updating Service Provider (SP) application settings will have the highest priority and we encourage administrators to get started with these updates right away.
Frequently Asked Questions
1. How will the tenant URL change?
2. Why is Idaptive transitioning to idaptive.app and not cyberark.com?
3. What is the final date for the transition?
4. Will there be any impact to end-users?
5. Will current applications require any updates?
6. Are any actions required for Endpoints - Mac, Windows, or mobile?
7. Are any actions required for the Connector?
8. Will there be any impact to MFA?
9. Are any actions required for Idaptive API's?
10. Is there any impact on Idaptive plug-ins?
11. Are any actions required for Directory Services (B2B Federation, Google Directory Service)?
12. What if I encounter issues during the transition and need assistance?
1. How will the tenant URL change?
Cloud Tenants will change to a URL suffix of idaptive.app. Idaptive plans to update all tenants to use a default Idaptive URL suffix during our 20.3 release, currently targeted for release end of August 2020. If a tenant is using a default URL of company.my.centify.com, the new preferred URL will be automatically updated to company.my.idaptive.app. The tenant URL suffix will change but customers can continue to use a company or custom URL prefix just as before. Changes to the default URL does not impact tenant functions, applications (including Office 365), or custom company URLs.
Administrators are recommended to update the preferred tenant URL to use *.idaptive.app before the 20.3 release. Idaptive has included an application report to display apps that may be using the centrify.com suffix but the default tenant URL must be changed to *.idaptive.app first before running the report with accurate results.
Idaptive has published article KB-8616: How to update the default Tenant URL to use idaptive.app that includes a brief quick Video with the easy steps to change the tenant URL.
2. Why is Idaptive transitioning to idaptive.app and not cyberark.com?
As part of the recent company acquisition of Idaptive by Idira in May 2020, Idaptive is required to discontinue the use of the cloud tenant domain centrify.com and will transition all customers to use idaptive.app by February 28th, 2021. Idira is now the legal owner of the idaptive.app domain but there are no plans to transition this branding to Idira domain naming. This is consistent with other Idira product offerings.
3. What is the final date for the transition?
Idaptive is planning to transition all cloud tenants to use a default tenant URL with idaptive.app during our 20.3 release, currently targeted for the end of August 2020 but will retain DNS for the centrify.com CNAME until February 28th, 2021. This should allow time for customers to update application metadata with service providers, endpoint enrollments, and API configurations.
4. Will there be any impact on end-users?
Administrators should communicate the URL change and device requirements to end-users to prevent future login issues after the legacy domain is removed in February 2021. Once the default tenant URL is updated, users should use and will see the new idaptive.app suffix in the browser address bar. All users, applications, or endpoints that continue to authenticate using centrify.com after the default tenant URL change will still function and are automatically directed to the Idaptive URL but only until February 28th, 2021, so user notification is important.
5. Will current applications require any updates?
Administrators must update all apps and SAML metadata with Service Providers (SP) to use Idaptive URLs. For more information, please see Idaptive article KB-8625: How to update application metadata to use an Idaptive URL suffix of idaptive.app or refer to our online documentation for configuring SAML SSO.
Administrators can log in to the Admin Portal and run the built-in application report named “Apps using Centrify Url” to retrieve a list of applications and app types that will need to be updated. Idaptive recommends running the report with a date range of 90 days to ensure infrequently used apps are not skipped The application URL updates are generally performed within the app Service Provider’s (SP) administration portal where SAML metadata URLs should be updated from using *.centrify.com to *.idaptive.app. Customers are encouraged to work with application owners and service providers early in case extra time is required for these changes.
Note for Customers that use Office 365. If the Office 365 app appears in the Centrify.com URL report, Administrators will need to navigate to the Office 365 app settings within the Admin Portal and Re-Federate all domains configured for use with Idaptive per article KB-8625: How to update application metadata to use an Idaptive URL suffix of idaptive.app . This will update your federation URLs and should be silent for users.
6. Are any actions required for Endpoints - Mac, Windows, or mobile?
Android and iOS endpoints that are used for SSO only and do not use the Idaptive Identity platform for mobile device management should not require any actions. This is managed by the Admin Portal device policy Endpoint Policies > Device Management Settings > Use the Idaptive Identity platform for mobile device management (default = Yes).
Android, iOS, Mac, and Windows endpoints enrolled for MDM will require different actions. For detailed information, please see Idaptive article KB-8629: How to update endpoints to use an Idaptive URL suffix of idaptive.app . The KB article includes instructions for creating an administrator report of devices that require actions before February 28th, 2021.
Device Actions Summary:
Android devices should update to the 20.3 Idaptive mobile app when released. After installing the 20.3 mobile app, no additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic.
iOS devices must unenroll and re-enroll with the cloud service before February 28th, 2021. When a device is re-enrolled using the Idaptive mobile app, it is important to verify the app settings are using a login URL of https://pod0.idaptive.app. After enrollment is complete, no additional actions are needed when the legacy URL is removed.
Mac computers that are enrolled using the Idaptive Mac Cloud Agent (MCA) should re-enroll with the cloud service before February 28th, 2021. After the Mac is re-enrolled, it is important to verify the MCA setting is using a login URL of https://pod0.idaptive.app. No additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic. Mac computers that were joined to Active Directory using the DirectControl agent and simultaneously enrolled with the cloud should unenroll and re-enroll using the Idaptive app. Note that users will need admin rights to perform enrollment.
Windows computers that are enrolled using the Idaptive Windows Cloud Agent (WCA) should update to the 20.4 WCA agent when released. After installing the 20.4 agent, no additional actions are needed when the legacy URL is removed and transition to idaptive.app will be automatic. Windows computers that were enrolled to the Idaptive Cloud using Microsoft's built-in device management client https://docs.idaptive.com/Content/Endpoints/EnrollEndpoints.htm should unenroll and re-enroll using a server URL of pod0.idaptive.app.
NOTE: Idaptive strongly recommends administrators to update and maintain Mac and Windows cloud agents, Idaptive Browser Extension (IBE), and the Idaptive mobile device app with the latest released versions. Keeping components up to date will ensure users receive the latest improvements and updates.
7. Are any actions required for the Connector?
A new connector feature will be included in 20.3 that will automatically manage the tenant URL change silently in the host registry. If administrators simply update to 20.3 connectors when released, no additional changes are required. If the installation of 20.3 is not possible, administrators must re-register all connectors using a hostname of pod0.idaptive.app. Connector versions below 20.3 that do not re-register will be unable to communicate with the cloud service once *.centrify.com is retired on February 28th, 2021.
8. Will there be any impact to MFA?
Customers that use FIDO2 or on-device authenticators require login to a specific tenant URL. It is recommended for customers to re-register these devices using the preferred URL of *.idaptive.app after changing from *.centrify.com.
Additionally, if you are using the ADFS plugin, admins must re-register the plugin by modifying the IdaptiveConfig.json to use the idaptive.app url and then restart the ADFS service.
9. Are any actions required for Idaptive API's?
Administrators can run a report named "APIs using Centrify Url" to display a list of APIs using Centrify URLs within a specific date range. Customers should update any API configurations to use idaptive.app by February 28th, 2021 to prevent any loss of functionality. For additional information, please refer to our API online documentation.
10. Is there any impact on Idaptive plug-ins such as ADFS, Confluence, or Jira?
Customers using Idaptive plugins for ADFS, AWS CLI, Bitbucket Server, Confluence Server, Jira Server, ServiceNow, and SharePoint Server SAML should refer to Idaptive online documentation for specific SSO application configuration steps.
11. Are any actions required for Directory Services (B2B Federation, Google Directory Service)?
Google Directory Service (GDS) by default will not require a change, but if you have a custom Whitelist in your GDS tenant you will need to update the Whitelist to include your new *.my.idaptive.app URL.
B2B Federations whether using SAML or WS-Fed protocol must update their metadata on both Idaptive and IDP side to use the *.idaptive.app URLs.
12. What if I encounter issues during the transition and need assistance?
If you encounter any issues or have questions related to updating applications or other tenant settings, Idaptive Support is the primary place to request assistance. Please log a case via our portal at https://cyberark-customers.force.com/s/ or call our support line at 408-495-8118 for urgent assistance.
Sometimes, the best way to solve a problem is to grant Idaptive support read-only access to your tenant so engineers can review your tenant configuration. For more information, please refer to Idaptive online documentation.