nextcloud / nextcloud/user_saml
Error: Account not provisioned - cannot login after update to version 7.0.0 or 7.1.0
Open
Nobody has claimed this yet.
0. Needs triage
bug
needs info
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
How to use GitHub
Steps to reproduce
- Setup nextcloud with user_saml
- upgrade user_saml to version 7.0.0
Expected behaviour
SAML authenticated users still are able to login
Actual behaviour
Generic error message "Account not provisioned" is appearing
Server configuration
Web server: Apache
Database: Maria
PHP version: 8.4
Nextcloud version: 31.0.8
List of activated apps
- activity: 4.0.0
- admin_audit: 1.21.0
- app_api: 5.0.2
- bruteforcesettings: 4.0.0
- calendar: 5.3.9
- circles: 31.0.0
- cloud_federation_api: 1.14.0
- comments: 1.21.0
- contacts: 7.2.5
- contactsinteraction: 1.12.0
- dashboard: 7.11.0
- dav: 1.33.0
- deck: 1.15.2
- federatedfilesharing: 1.21.0
- federation: 1.21.0
- files: 2.3.1
- files_downloadlimit: 4.0.0
- files_external: 1.23.0
- files_pdfviewer: 4.0.0
- files_reminders: 1.4.0
- files_sharing: 1.23.1
- files_trashbin: 1.21.0
- files_versions: 1.24.0
- fileslibreofficeedit: 2.0.1
- firstrunwizard: 4.0.0
- forms: 5.1.2
- groupfolders: 19.1.3
- logreader: 4.0.0
- lookup_server_connector: 1.19.0
- mail: 5.3.0
- memories: 7.6.2
- nextcloud_announcements: 3.0.0
- notes: 4.12.3
- notifications: 4.0.0
- oauth2: 1.19.1
- photos: 4.0.0
- privacy: 3.0.0
- profile: 1.0.0
- provisioning_api: 1.21.0
- recognize: 9.0.3
- recommendations: 4.0.0
- related_resources: 2.0.0
- serverinfo: 3.0.0
- settings: 1.14.0
- sharebymail: 1.21.0
- support: 3.0.0
- survey_client: 3.0.0
- systemtags: 1.21.1
- tasks: 0.16.1
- text: 5.0.0
- theming: 2.6.1
- twofactor_backupcodes: 1.20.0
- updatenotification: 1.21.0
- uppush: 2.3.0
- user_ldap: 1.22.0
- user_saml: 7.0.0
- user_status: 1.11.0
- viewer: 4.0.0
- weather_status: 1.11.0
- webhook_listeners: 1.2.0
- workflowengine: 2.13.0
Server log
Aug 20 19:13:26 nextcloud Nextcloud[95504]: {"reqId":"REMOVED","level":3,"time":"2025-08-20T17:13:26+00:00","remoteAddr":"REMOVED","user":"--","app":"user_saml","method":"POST","url":"/nextcloud/index.php/apps/user_saml/saml/acs","message":"The response was received at https://somehost/nextcloud/index.php/apps/user_saml/saml/index.php/apps/user_saml/saml/acs instead of https://somehost/nextcloud/index.php/apps/user_saml/saml/acs","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:128.0) Gecko/20100101 Firefox/128.0","version":"31.0.8.1","data":{"app":"user_saml"}}
Browser
Browser name: Firefox, Safari, TorBrowser
Browser version: (various)
Operating system: MacOS
Fixes for me
# diff vendor/onelogin/php-saml/src/Saml2/Utils.php.orig vendor/onelogin/php-saml/src/Saml2/Utils.php
659c659
< $infoWithBaseURLPath = self::buildWithBaseURLPath($route);
---
> $infoWithBaseURLPath = self::getBaseURLPath($route);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with vendor/onelogin/php-saml/src/Saml2/Utils.php and compare buildWithBaseURLPath with the reported getBaseURLPath workaround. Reproduce the SAML ACS login after upgrading user_saml, then verify that authenticated users can log in without the “Account not provisioned” error or the logged response-URL mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100