[
https://issues.apache.org/jira/browse/SYNCOPE-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1968:
--------------------------------------------
Description:
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.
was:
CAS provides some [initial support for
multitenancy|https://apereo.github.io/cas/development/multitenancy/Multitenancy-Overview.html].
WA should be able to map Syncope Domains to CAS tenants.
> 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: 0.5h
> 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)
