maslow/experiment-minio-with-oidc — explained in plain English
Analysis updated 2026-07-31 · repo last pushed 2022-09-05
Test single sign-on between MinIO and Casdoor locally before committing to a full deployment.
Let a small team manage file storage access through one central login instead of separate MinIO passwords.
Explore self-hosted infrastructure by running MinIO and Casdoor together with Docker Compose.
| maslow/experiment-minio-with-oidc | 0xallam/posthog | 0xallam/search-engine | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | — | Python | C++ |
| Last pushed | 2022-09-05 | 2026-03-26 | 2023-08-23 |
| Maintenance | Dormant | Maintained | Dormant |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 3/5 | 3/5 |
| Audience | pm founder | pm founder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Docker Compose plus manual configuration in the Casdoor admin interface and replacing placeholder credentials in the example scripts.
This repository is a small experiment for connecting MinIO (a self-hosted file storage system) with Casdoor (a user login and identity management tool). The goal is to let people sign into MinIO's admin console using their Casdoor username and password instead of a separate set of credentials. In other words, you get single sign-on: your users manage one login, and access to the storage system is tied to that central identity. At a high level, the project uses Docker Compose to spin up both MinIO and Casdoor together so you can test the integration locally. You start everything with a single command, then do some manual configuration in the Casdoor admin interface, creating an organization, setting up an application, and registering a callback URL so Casdoor knows where to send users after they log in. Then you run a few command-line scripts that tell MinIO to trust Casdoor as its login provider, pointing it at Casdoor's configuration URL and passing in the client ID and secret you created earlier. The target audience is someone evaluating how these two tools work together before committing to a full setup, maybe a founder or technical PM exploring self-hosted infrastructure, or a developer who needs MinIO for file storage but wants centralized user management rather than dealing with separate passwords. A concrete use case would be a small team that already uses Casdoor for logins and wants their file storage access controlled by the same system, assigning users roles like "readwrite" or "consoleAdmin" based on tags in Casdoor. The project is explicitly labeled an experiment, so it is not production-ready. The README includes placeholder credentials in its example scripts, which you would replace with your own. It does not go into detail on security considerations or production hardening, it is essentially a walkthrough for a local proof of concept.
A local experiment that connects MinIO (self-hosted file storage) with Casdoor (a login and identity management tool) so users can sign into MinIO using one set of credentials. It uses Docker Compose to spin up both services for testing the single sign-on integration.
Dormant — no commits in 2+ years (last push 2022-09-05).
No license information is provided in this repository, so usage rights are unspecified.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.