Files
Store files on the server and distribute them to your application.
Why Use Files?
You may want to distribute files to your application through Authgate for various reasons:
- Provide updates
- Download assets
- Enable premium features in a secure way
Public vs Private Files
The visibility of files behaves the same way as with variables. Private files are only accessible to authenticated users, while public files are accessible to anyone with your API key and secret.
Encryption
Files can be stored with or without encryption:
Plain Storage
Files are stored as-is on the server.
Encrypted Storage
- Files are encrypted on the server using AES-256 (GCM)
- Automatically decrypted in-memory by the SDK after download
- Extra security layer for sensitive content
Choose encryption when uploading the file. You can’t change it later without re-uploading.
Uploading Files
- Go to Files in your dashboard
- Click “Upload file”
- Choose your file or drag and drop it
- Enter a name
- Choose public or private
- Choose encrypted or plain storage
- Upload
The file is processed in the background. You’ll see the storage status update when ready.
Managing Files from CI/CD
Besides the dashboard, you can upload, replace, list, and delete files programmatically through the Admin API, authenticated with your Admin API Key. This is ideal for CI/CD pipelines that push new builds to Authgate automatically — including an upsert-by-name endpoint so a pipeline can push by a stable file name without tracking file IDs.
Each file shows a source badge in the files table indicating whether it was last written from the Dashboard or the Admin API, so you can tell CI-managed files apart from manually uploaded ones.
Downloading Files
You can download files from the dashboard by clicking the download button. The file will be served as-is (no automatic decryption).
Your application downloads files through the API using the file ID. The Authgate SDK handles authentication and decryption automatically.
See SDK documentation for examples.