Guides

Custom OAuth app

Most connectors sign you in with one click. Some, like GitHub, need an OAuth app that you create in that service first. You do this once per service.

When you’ll see this

When you add an account, a Create Custom OAuth Configuration window opens instead of a sign-in page.

Before you start

You need access to the service’s developer settings, so you can create an OAuth app there.

Set it up

1. In the service’s developer settings, create a new OAuth app.
2. Copy the redirect URI from the yellow box in Edge Connect. Add it to your OAuth app’s redirect or callback URLs. For GitHub it’s https://api.edgeconnect.cloud/auth/github/callback.
3. Copy the Client ID and Client Secret from your OAuth app.
4. In Edge Connect, give the configuration a name and paste the Client ID and Client Secret.
5. Click Save and connect. Sign in to the service and approve the access.

What each field means

• Configuration name: a name you’ll recognize, like “GitHub support team”.
• Client ID and Client Secret: the keys of your OAuth app. Keep the secret private.
• Required OAuth scopes: the permissions Edge Connect asks for. They’re shown so you know what you’re approving.
• Authorized redirect URI: where the service sends you back after you approve. It must match exactly.

Save only or Save and connect

Save and connect saves the configuration and opens the sign-in right away. Save only keeps the configuration so you can connect later.

If something goes wrong

• Redirect URI mismatch: the URL in your OAuth app doesn’t match the one in Edge Connect. Copy it again, with no extra spaces or slashes.
• Invalid client: check the Client ID and Client Secret. If you lost the secret, generate a new one in the service.