nextcloud / nextcloud/user_saml
multi tenancy with keycloak
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Server configuration
Operating system: Linux Alpine 3.7
Web server: Nginx + PHP_FPM
Database: MARIADB
PHP version: 7.1
Nextcloud version: 13.0.4
I wish there is a way to have the domain name as a variable in IdP settings. For instance, I have keycloak.contoso.com, and nextcloud.contoso.com. Ideally, I could just tell the webmaster of fabrikom.com to set his dns cname for keycloak.fabrikom.com to keycloak.contoso.com, as well as nextcloud.fabrikom.com to nextcloud.contoso.com. Suppose I have setup my keycloak server for multitenancy, one should be able to sign in to nextcloud.fabrikom.com just fine.
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
The issue names no files, tests, or entry points. Start by locating the SAML IdP settings and how the Nextcloud request host is handled; done would mean supporting tenant-specific domains for Keycloak and Nextcloud sign-in without breaking existing configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100