# SDK Key migration

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

The SDK Key and Secret in the Zoom App Marketplace are deprecated. Use the Client ID and Client Secret instead.

> **Migration deadline**
>
> We have chosen to postpone enforcement of the migration from the legacy Meeting SDK Key and Secret to the Client ID and Client Secret. We will communicate a new date at a later time.

Follow these steps to update your [JWT signature](/docs/meeting-sdk/auth/) to use the Client ID and Client Secret.

1. **Get your app credentials** - Log into the Zoom App Marketplace, go to **Manage**, select your Meeting SDK app, click **App Credentials**, and copy your **Client ID** and **Client Secret** in the App Credentials section, under the SDK Credentials section for your app. See [the screenshot](#meeting-sdk-app-credentials) for details.

2. **Update your signature generation** - Replace your SDK Key and SDK Secret with the Client ID and Client Secret [in your signature generation](/docs/meeting-sdk/auth/#generate-a-meeting-sdk-jwt), most likely in your environment variables.

3. **For the Meeting SDK for web only**, remove the `sdkKey` value from the `join` function as it is no longer required and [will cause errors in future versions](/changelog/meeting-sdk/web/4.0.0#action-required--future-breaking-change).

4. **Test your changes** - Verify that you can start and join meetings and webinars.

## Meeting SDK app credentials

The following screenshot shows where you can find your Client ID and Client Secret.

![Meeting SDK app credentials Client ID and Client Secret](/img/msdk-sdkKey-migration.png)

> **Meeting SDK JWT credentials**
>
> To generate the Meeting SDK JWT, use either development or production credentials and your **Client ID** and **Client Secret** app credentials. If you choose to publish your app, use production credentials.

## Conversion to general app

Your SDK app may offer, or may have already undergone, a one-time conversion to the new general app UI. If your app has been converted into a general app, you'll see the app credentials on the **App Info** page.

If your app is already published and you do not see **Start Conversion**, click **Publish Updates** to submit an update request and begin the conversion process.

Following conversion, the old **SDK Key** and **SDK Secret** will no longer be displayed. This is only a cosmetic change. Your app functionality is not affected. If you encounter issues during conversion, [contact Support](/support/).