[
https://issues.apache.org/jira/browse/SYNCOPE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794119#comment-13794119
]
Francesco Chicchiriccò commented on SYNCOPE-420:
------------------------------------------------
After playing a bit with source code, I've come to a semi-complete rethinking
of my comment above.
Basically, there is no solid reason to not implement any attribute value
transformation using PropagationActions or SyncActions (for cases (2) and (3)
above).
I will commit, anyway, an extension to implement the use case (1) above, even
though equal for both 1_1_X and trunk.
> Provide an attribute value pre-processing mechanism
> ---------------------------------------------------
>
> Key: SYNCOPE-420
> URL: https://issues.apache.org/jira/browse/SYNCOPE-420
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.1.5, 1.2.0
> Reporter: fabio martelli
> Assignee: Francesco Chicchiriccò
> Fix For: 1.1.5, 1.2.0
>
>
> Before storing/propagating/synchronizing a specific attribute it should be
> called an attribute value pre-processor in order to permit to manipulate each
> attribute value.
> The idea is to provide an interface to be implemented into the overlay in
> order to perform custom pre-processing operations.
> The custom implementation class name could be defined into the global
> configuration.
> This new feature would give the "handle" to provide several attribute value
> manipulation like specific value translations, or something else.
--
This message was sent by Atlassian JIRA
(v6.1#6144)