You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2019/05/15 06:53:00 UTC

[jira] [Resolved] (SYNCOPE-1456) New component: Keymaster

     [ https://issues.apache.org/jira/browse/SYNCOPE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò resolved SYNCOPE-1456.
---------------------------------------------
    Resolution: Fixed

> New component: Keymaster
> ------------------------
>
>                 Key: SYNCOPE-1456
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1456
>             Project: Syncope
>          Issue Type: New Feature
>          Components: keymaster
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 3.0.0
>
>
> This component serves three purposes:
>  # allow for [Service Discovery|https://dzone.com/articles/service-discovery-in-a-microservices-architecture] (Core needs to call SRA, Console needs to call Core and SRA, SRA needs to call Core, and so on)
>  # act as shared repository for [Configuration Parameters|http://syncope.apache.org/docs/reference-guide.html#configuration-parameters]
>  # allow for dynamic [Domain|http://syncope.apache.org/docs/reference-guide.html#domains] management, eliminating the need to restart / redeploy to onboard new Domains.
> It is needed to provide two distinct implementations of Keymaster:
>  * one - backed by an existing Open Source product as [Apache Zookeper|https://zookeeper.apache.org/] or [Consul|https://www.consul.io/] - to cover microservice deployment scenarios
>  * one "embedded" to keep covering ordinary, non-microservice deployment scenarios



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)