API Communication flow

When a user opens a protected file in the browser via Seclore Online, the flow is as follows.

1. 1 User clicks “Open in Browser” in the enterprise application.
2. 2 Application generates:
   • File Token
   • Access Token (scoped to user + file)
3. 3 Application redirects user to Seclore Online API endpoint.
4. 4 Seclore Online:
   • Validates tokens
   • Fetches file content from the enterprise application
5. 5 User is authenticated via Policy Server.
6. 6 Effective permissions are computed.
7. 7 File opens in view or edit mode (based on permissions).
8. 8 On save (optional):
   • Changes are sent back to enterprise application.
   • Version control and audit logs are updated.

Integration Endpoints Required by Enterprise Application

The enterprise application needs to implement below APIs:

• Check File - Fetches the metadata of the file
• Get File - Seclore Online expects actual file
• Download File - Enables user to download the file
• Init Edit - Application will initiate editing
• Put File (save-back) - Application saves back the updated file back
• Renew Access Token
• Open event endpoint
• Close event endpoint

These endpoints allow Seclore Online to securely communicate with the application for file retrieval and lifecycle management. For full request/response specifications, see the Developer Guide.