[
https://issues.apache.org/jira/browse/SYNCOPE-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128967#comment-18128967
]
ASF subversion and git services commented on SYNCOPE-1968:
----------------------------------------------------------
Commit d17d4ff7f584939d06341859aa6ac37a3dc2338c in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=d17d4ff7f5 ]
[SYNCOPE-1968] Map each SRA and WA instance to a single Domain (#1517)
> Support multitenancy for WA and SRA
> -----------------------------------
>
> Key: SYNCOPE-1968
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1968
> Project: Syncope
> Issue Type: New Feature
> Components: sra, wa
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 5.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> CAS provides some [initial support for
> multitenancy|https://apereo.github.io/cas/development/multitenancy/Multitenancy-Overview.html].
> While this looks like a good option to map Syncope Domains, it looks like it
> is not meant to provide separate configurations (including authentication
> handlers, attribute repositories, applications, etc.) per tenant.
> Hence, the most suitable implementation option seems to be to bind each WA
> instance to a given Syncope Domain, where all those configurations are meant
> to be managed.
> The same for SRA.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
