[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464953#comment-15464953 ]
ASF subversion and git services commented on SYNCOPE-880: --------------------------------------------------------- Commit f17be3cf91d484595a632d01761a62b1b1d29b34 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f17be3c ] [SYNCOPE-880] Cleanup, finalize, rework - This closes #26 > Identity Recertification > ------------------------ > > Key: SYNCOPE-880 > URL: https://issues.apache.org/jira/browse/SYNCOPE-880 > Project: Syncope > Issue Type: New Feature > Components: core > Reporter: Nicola Scendoni > Assignee: Nicola Scendoni > Priority: Minor > Fix For: 2.0.0 > > > 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)