A user successfully logs in to a website that hosts data (mp4 files) on a Seafile 13 Pro server. To be able to upload new data, it would be desirable for this user not to have to log in to the Seafile 13 Pro server again. The Seafile 13 Pro server runs in a Docker container. The Seafile 13 Pro web GUI is publicly accessible via an Apache2 reverse proxy.
If your Web App can act as an OAuth2 Provider (or if both apps can use a common provider like Keycloak or Authentik), you can configure Seafile as an OAuth client. This allows users to log in to Seafile with a single click, or automatically if the session is active.
Detailed guides for these methods can be found in the Seafile Admin Manual: