Missing oc_share entries for SAML-provisioned users in existing groups after SAML-provisioning
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- mariadb, php
- Área
- authentication, authorization, databases
Línea de trabajo
Comienza reproduciendo el aprovisionamiento de SAML en un grupo existente con una carpeta compartida; después, inspecciona cómo se gestionan las adiciones a oc_group_user y si se generan las entradas correspondientes en oc_share. Compara la ruta de aprovisionamiento con la adición manual de un usuario a un grupo; el issue estará terminado cuando los usuarios aprovisionados o asignados recientemente puedan acceder a los recursos existentes compartidos con el grupo sin la solución alternativa del trigger de base de datos.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Provision a new user via SAML and ensure they are automatically assigned to an existing group (e.g., Group A) that has shared folders (e.g., Folder A).
- Log in as the newly provisioned user.
- Verify whether the group-shared folder (e.g., Folder A) is visible and accessible to the user.
Alternative scenario:
- Log in as an existing user.
- Assign the user to a new SAML-provisioned group (e.g., Group B) that has shared folders (e.g., Folder B).
- Verify whether the newly assigned group-shared folder (e.g., Folder B) is visible and accessible to the user.
Expected behaviour
When a user is added to a SAML-provisioned group, shared folders and files that were previously assigned to the group should be automatically available to the new user. Entries in the oc_share table should be generated accordingly, ensuring access to group-shared resources.
For example:
- Folder A is shared with Group A.
- User X is added to the system and automatically assigned to SAML Group A.
- User X should immediately see Folder A and have access to the shared content, with corresponding entries in the oc_share table.
Actual behaviour
Currently, when a new user is provisioned via SAML and added to an existing group (e.g., Group A), the group-shared files and folders (e.g., Folder A) do not appear for the user. Although the share exists, no entries are created in the oc_share table to provide access.
If you manually add the user to the group through the Nextcloud backend or reassign the permissions on the folders, the oc_share entries are correctly created, and the user gains access to the shared resources.
This issue did not exist in version 5.27 but appears to be a regression in the current version.
Workaround (temporary fix):
In my instance, I’ve created a trigger for the oc_group_user table that temporarily addresses the issue. The trigger ensures that whenever a new gid-uid combination is added, the corresponding entries in the oc_share table are created or deleted accordingly. However, this should not be considered a permanent solution, as it only works as a temporary fix to handle the missing share entries in this specific instance.
Server configuration
Official Nextcloud Docker (nextcloud:30)
Web server: Apache/Nginx
Database: MariaDB
PHP version: 8.2.24
Nextcloud version: 30.0.0
- Lenguaje dominante
- PHP
- Estrellas
- 106
- Forks
- 84
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 14
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/user_saml
-
Logout link is empty in environment-variable mode without login form (regression from #1235)Abierto0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
-
0. Needs triage bug
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
Los mantenedores suelen responder en 1 día
Todos los issues de nextcloud/user_saml
Issues similares
-
Modules list cache misses every hour because it is keyed on the hourly accounts tokenPosiblemente ocupada @SachaFARINEL la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
PrestaShopCorp/ps_mbo#899 ·
-
enhancement priority Sales
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
novalo-dev/Prestashop-MCP-Server#201 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
web-token/jwt-framework#757 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 82/100
WordPress/Documentation-Issue-Tracker#2562 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día