ShareFile - COPY

ShareFile is a secure content collaboration, file sharing, and sync software that supports document-centric tasks and workflow needs of small and large businesses. The company also offers cloud-based or on-premises storage, virtual data rooms, and client portals.

ShareFile is owned by Citrix Systems. In order to integrate ShareFile with Relyance AI you will need a Subdomain, Client ID, and Client Secret and to follow an OAuth2 flow.

In ShareFile:

1. Login to your ShareFile account to verify your subdomain. Your subdomain value is the prefix to your ShareFile domain (e.g., if your domain is yourcompany.sharefile.com then your subdomain is yourcompany).
2. Login to https://api.sharefile.com/apikeys with your subdomain and ShareFile account credentials.
3. Click Get an API Key.
4. Click the Create New button.
5. Enter an Application Name for the integration application (e.g. RelyanceAI).
6. Tick the box for I don't know or will not use a Redirect URI.
7. Click Generate Api key.
8. Temporarily save the client ID and client secret for later configuration steps.

In Relyance AI:

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the ShareFile integration card and click on it.
5. Click on the Add Connection button on the top right.
6. Provide a meaningful name for the integration and click on the Add button.
7. In the Overview section, select the integration features you wish to enable for the integration, review the Scope and Permission, and Endpoint details and click on Continue. For more details, see Integration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, Please choose the authentication method as Oauth2 / App Token and provide the following information retrieved from the In ShareFile section and click on Authenticate.
10. Review the configuration summary from the Completion section and click on Finish.
11. Confirm the integration Status reflects Connected.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
3. Check the address fields before suspecting the credentials. Subdomain identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Authentication methods and fields

Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example citrix_sharefile/<connection_id>) or reading it with the relyance_integration_connection data source.