You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Giacomo Lamonaco (JIRA)" <ji...@apache.org> on 2014/12/23 14:54:13 UTC
[jira] [Created] (SYNCOPE-624) Provisioning manager integration
Giacomo Lamonaco created SYNCOPE-624:
----------------------------------------
Summary: Provisioning manager integration
Key: SYNCOPE-624
URL: https://issues.apache.org/jira/browse/SYNCOPE-624
Project: Syncope
Issue Type: New Feature
Components: common, console, core
Reporter: Giacomo Lamonaco
Assignee: Giacomo Lamonaco
Fix For: 1.3.0
Hi all,
last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager.
Initially I submitted a request to dev@syncope: in this discussion [1] you can read all the tecnical details. Amongst other things, in this proposal I thought to use Apache Camel as base of the provisioning manager. In the subsequent 3/4 months, with the help of a talented Camel commiter, I obtained something that looks interesting. We decided to make provisioning pluggable: in this way user decide the default provisioning engine. Moreover a the end of this work we provided some console feature, in order to change provisioning definitions - only in the Camel case btw.
Some days ago, I tried to merge all my modifications with the current version of Syncope: after some days of work, everything is back to work. I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work.
[1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html
[2] https://github.com/apache/syncope/pull/2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)