syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colm O hEigeartaigh <cohei...@apache.org>
Subject Re: Syncope clustering
Date Fri, 04 Mar 2016 10:55:59 GMT
Thanks Francesco for the feedback.

Colm.

On Fri, Mar 4, 2016 at 7:52 AM, Francesco Chicchiriccò <ilgrosso@apache.org>
wrote:

> On 03/03/2016 18:23, Colm O hEigeartaigh wrote:
>
>> Hi all,
>>
>> The Syncope cluster page* gives information about deploying multiple
>> Syncope instances sharing the same database, and then gives some
>> information about Tomcat clustering.
>>
>> Just wondering what the benefit is, if any, to setting up a Tomcat
>> cluster,
>> if you don't need session replication? Wouldn't the first scenario suffice
>> for load balancing, or am I missing something?
>>
>
> Hum, I believe you are right: as you point out correctly, Syncope core
> does not manage any kind of user sessions - while console does; we should
> change that wiki page to reflect this difference.
>
> As for core not managing sessions, changes on such topic are indeed in the
> roadmap (SYNCOPE-699 being currently set for 2.1):
>
>
> https://cwiki.apache.org/confluence/display/SYNCOPE/[DISCUSS]+Apache+Shiro+integration+for+authentication+and+authorization
> <https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Apache+Shiro+integration+for+authentication+and+authorization>
>
> As reported in my comment there, not sure if Shiro is still the best
> option, but we'll see when the work for 2.1 is actually going to start - at
> the moment all efforts are towards 2.0.
>
> Regards.
>
> *
>>
>> https://cwiki.apache.org/confluence/display/SYNCOPE/Setup+a+Syncope+cluster
>>
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
> http://home.apache.org/~ilgrosso/
>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message