nextcloud / nextcloud/user_saml

Enhancement: Option to allow quotas set in NC to override the SAML quota

Open
#327 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
104
Forks
85
Avg merge
1d 15h
Merged PRs (30d)
16

Description

Was having issues with both this and roles. I saw PR #311, and was wondering if we could have something here as well that respected the changes done on the nextcloud side.

Steps to reproduce
  1. Start with base, functioning nextcloud + saml, with a mapped quota attribute
  2. Set quota on saml user, log in with that user, and verify that that quota takes effect
  3. As admin, manually change that users quota
  4. Log in with the saml user, and see that the quota has been reset.
Expected behaviour

The quota should stick to the new value set via nextcloud interface.
Should possibly be an option to use the quota attribute as a default value.

Actual behaviour

The quota stays at the value defined in saml.

Server configuration

Keycloak + Nextcloud 15.0.7 + PHP 7.2

Operating system: Ubuntu 18.10

Web server: Nginx

Database: MariaDB

PHP version: 7.2

Nextcloud version: 15.0.7

Where did you install Nextcloud from: Tarball

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing PR #311 and the existing SAML quota-mapping behavior described in the reproduction steps. Trace where the mapped quota is applied during login and determine how a Nextcloud-set quota could take precedence. Done means an option or behavior allows the manually changed Nextcloud quota to persist while retaining a configurable SAML quota default.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authentication
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.