> [!CAUTION]
> You are currently viewing version 1.11 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.11 </button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/helm-install-enable-synchronizer-access.html)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/helm-install-enable-synchronizer-access.html)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/helm-install-enable-synchronizer-access.html)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/helm-install-enable-synchronizer-access.html)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/helm-install-enable-synchronizer-access.html)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/helm-install-enable-synchronizer-access.html)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-enable-synchronizer-access.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/helm-install-enable-synchronizer-access.html)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/helm-install-enable-synchronizer-access.html)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/helm-install-enable-synchronizer-access.html)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/helm-install-enable-synchronizer-access.html)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/helm-install-enable-synchronizer-access.html)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/helm-install-enable-synchronizer-access.html)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/helm-install-enable-synchronizer-access.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/helm-install-enable-synchronizer-access.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/helm-install-enable-synchronizer-access.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/helm-install-enable-synchronizer-access.html)

## Get an authorization token


To make the Apigee API calls described later in this topic, you need to get an authorization
token that has the Apigee Organization Admin role.

1. If you are not the owner of the Google Cloud project that is associated with your Apigee hybrid organization, be sure that your Google Cloud user account has the **roles/apigee.admin** (Apigee Organization Admin) role. You can check the roles assigned to you with this command:

   ```
   gcloud projects get-iam-policy ${PROJECT_ID}  \
     --flatten="bindings[].members" \
     --format='table(bindings.role)' \
     --filter="bindings.members:your_account_email"
   ```


   For example:

   ```
   gcloud projects get-iam-policy my-project  \
     --flatten="bindings[].members" \
     --format='table(bindings.role)' \
     --filter="bindings.members:myusername@example.com"
   ```


   The output should include `roles/apigee.admin`.
2. If you do not have `roles/apigee.admin`, add the **Apigee
   Organization Admin** role to your user account. Use the following command to add the role to your user account:

   ```
   gcloud projects add-iam-policy-binding ${PROJECT_ID} \
     --member user:your_account_email \
     --role roles/apigee.admin
   ```


   For example:

   ```
   gcloud projects add-iam-policy-binding my-project \
     --member user:myusername@example.com \
     --role roles/apigee.admin
   ```
3. On the command line, get your `gcloud` authentication
   credentials using the following command:

   ### Linux / MacOS

   ```
   export TOKEN=$(gcloud auth print-access-token)
   ```

   To check that your token was populated, use `echo`, as the
   following example shows:

   ```
   echo $TOKEN
   ```

   This should display your token as an encoded string.

   ### Windows

   ```
   for /f "tokens=*" %a in ('gcloud auth print-access-token') do set TOKEN=%a
   ```

   To check that your token was populated, use `echo`, as the
   following example shows:

   ```
   echo %TOKEN%
   ```

   This should display your token as an encoded string.

## Enable synchronizer access


To enable synchronizer access:

1. Get the email address for the service account to which you are granting synchronizer access. For non-production environments (as suggested in this tutorial) it should be `apigee-non-prod`. For production environments, it should be `apigee-synchronizer`. Use the following command:

   ```
   gcloud iam service-accounts list --project ${PROJECT_ID} --filter "apigee-synchronizer"
   ```
2. Call the [setSyncAuthorization](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations/setSyncAuthorization.md.txt) API to enable the required permissions for Synchronizer using the following command:

   ```
   curl -X POST -H "Authorization: Bearer ${TOKEN}" \
     -H "Content-Type:application/json" \
     "https://apigee.googleapis.com/v1/organizations/${ORG_NAME}:setSyncAuthorization" \
      -d '{"identities":["'"serviceAccount:apigee-synchronizer@${ORG_NAME}.iam.gserviceaccount.com"'"]}'
   ```


   Where:
   - **`${ORG_NAME}`**: The name of your hybrid organization.
   - **`apigee-synchronizer${ORG_NAME}.iam.gserviceaccount.com`**: The email address of the service account.

   > [!TIP]
   > **Tip:** Some shells may return an error like `bad substitution`. In this case, replace <var translate="no">${ORG_NAME}</var> with the name of your organization and replace the `"'"` with `"` as follows:
   >
   > ```
   > curl -X POST -H "Authorization: Bearer $TOKEN" \
   >   -H "Content-Type:application/json" \
   >   "https://apigee.googleapis.com/v1/organizations/YOUR_ORG_NAME:setSyncAuthorization" \
   >    -d '{"identities":["serviceAccount:apigee-synchronizer@YOUR_ORG_NAME.iam.gserviceaccount.com"]}'
   > ```

3. To verify that the service account was set, use the following command to call the API to get a list of service accounts:

   ```
   curl -X GET -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type:application/json" \
     "https://apigee.googleapis.com/v1/organizations/${ORG_NAME}:getSyncAuthorization"
       
   ```


   The output looks similar to the following:

   ```
   {
      "identities":[
         "serviceAccount:apigee-synchronizer@my_project_id.iam.gserviceaccount.com"
      ],
      "etag":"BwWJgyS8I4w="
   }
   ```

   > [!NOTE]
   > **Note:** The call to the Apigee API uses <var translate="no">${ORG_NAME}</var>, and the results from the IAM service account mappings use <var translate="no">my_project_id</var>. In most cases, the values are the same. One uncommon exception is when using a [multi-org cluster](https://docs.cloud.google.com/apigee/docs/hybrid/latest/multi-org), where there would be more than one org name, and the service accounts could be different per org.

You have now enabled your Apigee hybrid runtime and management planes to
communicate. Next, install cert-manager to enable Apigee hybrid to interpret and manage
certificates.
[1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-create-cluster.md.txt) [2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-download-charts.md.txt) [3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-create-namespace.md.txt) [4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-service-accounts.md.txt) [5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-create-tls-certificates.md.txt) [6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-create-overrides.md.txt) [7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-enable-synchronizer-access.md.txt) [(NEXT) Step 8: Install cert-manager](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-cert-manager.md.txt) [9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-crds.md.txt) [10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-check-cluster.md.txt) [11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-helm-charts.md.txt) [12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/helm-install-workload-identity.md.txt)

<br />