Real bug caught by an end-to-end OIDC login test on dev3: apiserver accepts the JWT (auth succeeds) but the RBAC check fails with 403 because the CRB `User:` subject was `alice-oidc@test3.example` (from `users[].email`) but the apiserver-visible identity was `alice-oidc` (from `preferred_username`, which in the cozy realm is the Keycloak *username*, not the email). The design proposal example used `claim: preferred_username`, but the operator-facing `users[].email` field explicitly asks for the email address. In the cozy realm — verified — `preferred_username` is the Keycloak username (`kvaps`, `i.okhotnikov`), so the two do NOT coincide. Every user whose Keycloak username differs from their email would silently 403 after a successful OIDC handshake. Switch the AuthenticationConfiguration `claimMappings.username.claim` to `email`, aligning the apiserver-visible identity with the operator-declared `users[].email`. Every conformant OIDC provider emits `email` — cozy realm does (verified), and any BYO `CustomConfig` issuer that follows OIDC does too. The switch is invisible to installers where `preferred_username` already equals the email (a common Keycloak setup); for installers where it doesn't, this fix is required for RBAC to work at all. Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.
