> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect Egnyte with OAuth 2.0 (Internal Application) – StackOne Hub > Link a Egnyte account in the StackOne Hub using OAuth 2.0 (Internal Application). End-user guide to authorize the integration and start using Egnyte actions. Requires a Domain Admin account and an Internal Application registered on the Egnyte Developer Portal for the customer's Egnyte domain. The Egnyte plan must be an eligible plan — Trial, Legacy Office, or Team plans are not supported. Egnyte recommends this flow only for trusted, first-party integrations; use the OAuth 2.0 (Public Application) flow for multi-tenant integrations.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Register an Internal Application on the Egnyte Developer Portal

To connect Egnyte with StackOne using the Resource Owner Password Credentials grant, you need to create an Internal Application on the Egnyte Developer Portal. This will generate the API Key and API Secret required for integration, which map to `client_id` and `client_secret` in the token request.

Open your browser and navigate to the Egnyte Developer Portal. Click Sign In in the top-right corner, then enter your Email and Password and click SIGN IN. Use an account tied to an active Egnyte Domain Admin — API keys requested by a non-admin will be declined.

Egnyte Developer Portal sign-in form with Email and Password fields

Click your account email in the top-right corner to open the account dropdown, then click Apps. You land on the My Apps page.

Account dropdown showing the Apps menu item on the Egnyte Developer Portal

On the My Apps page, click + NEW APP in the top-right corner to open the New App form.

My Apps page with the + NEW APP button in the top-right

Complete the Overview section of the New App form. The Registered OAuth
Redirect URI field is not required for Internal Applications — leave it blank — and
Current User Base and Platform can stay at their defaults.

  • App Name — a display name for the app (for example, `Internal Integration`).
  • Description — a short description of the integration.
  • Egnyte Domain — the customer's Egnyte subdomain, without the `.egnyte.com` suffix. For example, from `https://acme.egnyte.com` enter `acme`. Trial domains are not eligible for API keys.
  • App Icon URL (optional) — URL to an image file (PNG, max 100px by 100px).
  • Type — choose Internal Application. Egnyte reserves this type for apps "built by Egnyte customers for use within their own organization" and enables the Resource Owner Password Credentials grant on the issued key. The Redirect URI is only used by Publicly Available Application — leave it blank here.
Egnyte New App form showing App Name, Description and Additional Information fields
Enables actions: Add Comment, Chunked Upload By File ID, Create Group, Create Link (v1), Create User, Delete Comment, Delete File Or Folder (v2), Delete File Or Folder By ID, Delete Group, Delete Link (v1), Delete User, Download File Content By ID, Download File Content By Path, File Or Folder Operation (v2), File Or Folder Operation By ID, Get Comment, Get Effective Permissions For User, Get Events Cursor, Get File Or Folder Metadata (v2), Get File Or Folder Metadata By ID, Get Folder Statistics By ID, Get Group, Get Link (v1), Get User, Get User Info, List Comments, List Events (v2), List Groups, List Links (v2), List Trash Contents (v2), List Users, Modify Folder Options, Partially Update Group, Replace Group, Restore Or Purge Trash Items, Search Files And Folders (v2), Update User, Upload File Content By Path

Scroll to the APIs section and click Request on the row for Prod Collaborate — this API grouping covers filesystem, comments, links, permissions, users, groups, search, trash, and events. Also request Prod\_SnG if the integration needs Secure & Govern APIs. Enable the scopes required for your use case:

APIs section on the New App form showing Prod Collaborate with the Request button

Click SAVE at the bottom-right of the form. For Internal Applications Egnyte issues the API Key and API Secret immediately with Status: Approved — no external review queue applies to internal keys on eligible plans.

Open the app from My Apps and scroll to the API Keys section on the app profile.

  • In the Key column, click the copy icon (Copy API key) to copy the API Key. This value maps to `client_id` in the token request.
  • In the Secret column, click Show secret to reveal the API Secret, then click the copy icon (Copy secret) to copy it. This value maps to `client_secret` in the token request. All Egnyte keys issued after January 2015 require a secret.
  • Paste the API Key into the API Key field on the StackOne Linked Account.
  • Paste the API Secret into the API Secret field on the StackOne Linked Account.
App profile API Keys section with Copy API key and Show secret controls

Find the Egnyte Domain

Every Egnyte account is scoped to a unique subdomain of `egnyte.com`. StackOne needs that subdomain to build the token URL (`https://{domain}.egnyte.com/puboauth/token`) and every subsequent API endpoint.

Open your browser and go to the customer's Egnyte sign-in URL — the address they normally use to reach Egnyte, in the form `https://acme.egnyte.com` (replace `acme` with the customer's subdomain).

On the Egnyte Sign in page (and in the browser address bar) you will see the workspace URL. The part before `.egnyte.com` is the Egnyte Domain. For example, if the sign-in page shows `app4stackone.egnyte.com`, the Egnyte Domain is `app4stackone`.

  • Enter only the subdomain part — omit any scheme prefix, the `.egnyte.com` suffix, and any trailing path.
  • The domain contains only letters, numbers, and hyphens — no spaces or special characters.
  • Trial domains are not eligible for the Egnyte Public API.
Egnyte tenant sign-in page showing the workspace name and the tenant subdomain

Paste the subdomain into the Egnyte Domain field on the StackOne Linked Account.

Prepare Domain Admin credentials for the password grant

The Resource Owner Password Credentials grant exchanges a Domain Admin's username and password for a token pair. Prefer a dedicated integration user account so token revocation doesn't disrupt individual admins, and rotate the credentials if they are ever exposed.

Only Domain Admins on the customer's Egnyte tenant can be exchanged for tokens with the required API scopes. Record the account's Egnyte login Username (not email address) and Password.

Paste the Domain Admin username into the Egnyte Username field and the password into the Egnyte Password field. These values are sent as `username` and `password` in the `grant_type=password` request to `/puboauth/token`. If Egnyte returns a `403 INVALID_USERNAME_OR_PASSWORD` error, retest with a password that has no special characters — Egnyte docs flag form-encoding edge cases here.

Linking the Account from the Hub

Use one of the three Linking Account Methods to access the Hub. Fill out the following fields using details from your provider:
  • Egnyte Domain
  • API Key
  • API Secret
  • Egnyte Username
  • Egnyte Password
  • OAuth Scopes (Optional)
  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.