[ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416716#comment-15416716 ]
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_r74380553 --- Diff: core/persistence-api/src/main/java/org/apache/syncope/core/persistence/api/entity/user/User.java --- @@ -96,4 +96,12 @@ List<? extends Role> getRoles(); + String getLastRecertificator(); + + void setLastRecertificator(String lastRecertificator); + + Date getLastRecertificion(); --- End diff -- Fix spell: `getLastRecertification()` > 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)