Change to existing API Key after migrating to Single Sign on

Will there be any change to my existing API Key after migration to Single Sign on

The current API Key of your account will remain the same after the Single Sign On migration, except that we will call it as Device Key henceforth. 

You can access Device Key by logging to Site24x7 web client and navigating to Admin > Developer > Device Key
    • Related Articles

    • How secure is Single Sign on migration

      The migration of existing Site24x7 accounts to Zoho Single Sign-On is highly secure and there is no possibility of your account getting compromised. Site24x7 is part of the Zoho family. We already share the same data center as Zoho, whose Single Sign ...
    • DC migration steps for APM Insight agents

      For Server based installations 1. Obtain the new device key. 2. Update the license.key value in the APM Insight configuration file (or the environment variable mentioned) with the new device key. The location varies for each agent, as listed below: ...
    • Update my DeskApp after migrating to Zoho Single Sign On

      After migration to Single Sign On, you need to update the DeskApp in your Site24x7 account. If you are already logged in, you will see a notification regarding the update inside your DeskApp client If you are launching the DeskApp afresh, you will be ...
    • Update Recorder Tool in Web Transaction Monitor after Single Sign On migration

      After migration to Zoho Single Sign-On, uninstall the existing Web Transaction Monitor's recorder (Site24x7_Recorder) and install the new version. Follow the below instructions: To uninstall the existing Recorder Tool In your Windows system, go to ...
    • DC migration steps for APM Insight Ruby agent

      Obtain the new device key. Update the license.key value in the apminsight.conf file located at <APP_HOME>/. Log in to the server and delete the existing instance information file, apminsight.info, located at <APP_HOME>/. Restart the Ruby application. ...