> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SonicWall Cloud Secure Edge

> Connect SonicWall Cloud Secure Edge (formerly Banyan Security) to Triggr with a Command Center API key.

Triggr manages Cloud Secure Edge (CSE, formerly Banyan Security) users, devices, services, policies, roles, access tiers and events; in Triggr it's called SonicWall CSE. For firewalls, use [SonicWall](/integrations/sonicwall/sonicos) or [SonicWall NSM](/integrations/sonicwall/nsm).

## Set up CSE

<Steps>
  <Step title="Add an API key">
    In the Command Center at `https://net.banyanops.com`, go to **Settings > Identity and Access > API Keys** (or Settings > API Keys in older versions), click **Add API Key** and name it `Triggr`.
  </Step>

  <Step title="Choose the scope">
    Admin can manage and read everything; ReadOnly only reads; ServiceAuthor, PolicyAuthor and EventWriter sit in between. See SonicWall's [API key privileges](https://cse-docs.sonicwall.com/docs/manage-admins/api-keys/).
  </Step>

  <Step title="Copy the secret">
    Copy the API Key Secret.
  </Step>
</Steps>

## Connect it in Triggr

<Steps>
  <Step title="Open the configuration">
    Go to **Integrations > SonicWall CSE** and click **Configure** on the Base Configuration card.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=bb81acb082055015f91beda7b4876f35" alt="The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button." width="2272" height="330" data-path="images/integrations-common/base-configuration.png" />
    </Frame>
  </Step>

  <Step title="Enter the secret">
    Paste the secret into API Key Secret and click Save Configuration.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/sonicwall-cse/configure.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=e99f9a4a407fad26f292d9925780dabf" alt="The SonicWall CSE configuration window with an API Key Secret field, an Allow insecure TLS switch under Advanced, and a Save Configuration button." width="1344" height="962" data-path="images/sonicwall-cse/configure.png" />
    </Frame>
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="401 errors">
    Check the secret was pasted in full and the key still exists under API Keys, or paste a fresh secret.
  </Accordion>

  <Accordion title="403 errors">
    The key's scope doesn't allow the action. Create a key with a scope that does, such as Admin.
  </Accordion>

  <Accordion title="404 errors">
    Get IDs from the same org with the matching list action, such as List services or List roles.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.