Varun Patil
Varun Patil
> This is because those are different user bases, hosted at different places. Regardless, why does that require you to deploy a _new_ OIDC instance? Isn't this a one-time config?
You should be supplying the quota from the OIDC provider if you want different quotas for different users. See `ownCloudQuota` in the readme.
You'll have to patch the code I guess. Maybe someone could work on this and have an option to set user quota on on user creation depending on a config...
Can you trace where the error is coming from? Can't repro, but I suspect this isn't related to this plugin.
Maybe the issue is with the order of the user logging in and the groups changing? Strictly speaking, this is a bug somewhere upstream, though.
Let's keep it open, I want to investigate this when time permits.
Ideally, you must do this on the OIDC provider side. But I don't mind accepting a PR for this, if it checks - * The presence of a key *...
I've no experience with KeyCloak, but there should be some form of RBAC. Your particular case is covered by the scheme I proposed too, where your key becomes `allow_nextcloud_access` and...
> Is the encryption app in general supported in combination with the oidc-login? I'm not aware of the internals of the encryption app, but assuming it uses the user's password...
This is the job of the OIDC provider