[
https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389013#comment-15389013
]
ASF GitHub Bot commented on SYNCOPE-880:
----------------------------------------
Github user ilgrosso commented on a diff in the pull request:
https://github.com/apache/syncope/pull/26#discussion_r71832801
--- Diff: core/persistence-jpa/src/test/resources/domains/MasterContent.xml
---
@@ -461,7 +470,15 @@ under the License.
<SyncopeSchema id="mderToBePropagated"/>
<DerSchema id="mderToBePropagated" expression="mderived_sx + '-' +
mderived_dx"
anyTypeClass_id="generic membership"/>
-
+
+ <SyncopeSchema id="lastRecertification"/>
--- End diff --
We should probably better handle `lastRecertification` and
`lastRecertificator` rather as `User` / `JPAUser` fields rather than schemas.
> Identity Recertification
> ------------------------
>
> Key: SYNCOPE-880
> URL: https://issues.apache.org/jira/browse/SYNCOPE-880
> Project: Syncope
> Issue Type: New Feature
> Components: console, core
> Reporter: Nicola Scendoni
> Priority: Minor
>
> Identify Re-certification is required for many national and international
> standards like SOX, GxP, etc.
> The idea is to implement one scheduled task that filter users basing on some
> attributes (example: last recertification date, role,...) and move then on
> one state "to be certified" and assign one task to some group that has the
> responsibility to recertified the user, or delete it from the system.
> Some report should report evidence about when the users have been recertified
> and who was the certifier.
>
> This feature would be also the starting point to create account, role and
> groups re-certifications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
