3 Commits (5dfa9a542ce957d610bf03a14e00eb94924ed6c8)

Author	SHA1	Message	Date
Paul Fitzpatrick	e564d31582	(core) give preliminary support in core for storing snapshots in S3-compatible stores via minio-js client ... Summary: This is a first pass at snapshot support using the MinIO client, suitable for use against a MinIO server or other S3-compatible storage (including the original AWS S3). In Grist Labs monorepo tests, it is run against AWS S3. It can be manually configured to run again a MinIO server, and these tests pass. There are no core tests just yet. Next step would be to move external storage tests to core, and configure workflow to run tests against a transient MinIO server. Test Plan: applied same tests as for Azure and S3 (via AWS client) Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D3729	2 years ago
Paul Fitzpatrick	561d9696aa	(core) clean up interaction of forward auth with session ... Summary: For self-hosted Grist, forward auth has proven useful, where some proxy wrapped around Grist manages authentication, and passes on user information to Grist in a trusted header. The current implementation is adequate when Grist is the only place where the user logs in or out, but is confusing otherwise (see https://github.com/gristlabs/grist-core/issues/207). Here we take some steps to broaden the scenarios Grist's forward auth support can be used with: * When a trusted header is present and is blank, treat that as the user not being logged in, and don't look any further for identity information. Specifically, don't look in Grist's session information. * Add a `GRIST_IGNORE_SESSION` flag to entirely prevent Grist from picking up identity information from a cookie, in order to avoid confusion between multiple login methods. * Add tests for common scenarios. Test Plan: added tests Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D3482	2 years ago
Paul Fitzpatrick	1c6f80f956	(core) make it easier to enable Azure storage without setting GRIST_DOCS_S3_BUCKET ... Summary: Previously, absence of `GRIST_DOCS_S3_BUCKET` was equated with absence of external storage, but that is no longer true now that Azure is available. Azure could be used by setting `GRIST_DOCS_S3_BUCKET` but the alternative `GRIST_AZURE_CONTAINER` flag is friendlier. Test Plan: confirmed manually that Azure can be configured and used now without `GRIST_DOCS_S3_BUCKET` Reviewers: alexmojaki Reviewed By: alexmojaki Subscribers: alexmojaki Differential Revision: https://phab.getgrist.com/D3448	2 years ago