[
https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434392#comment-15434392
]
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_r76007411
--- Diff: pom.xml ---
@@ -197,6 +197,16 @@ under the License.
<url>http://people.apache.org/~anzelld/</url>
</developer>
<developer>
+ <id>anzelld</id>
+ <name>Nicola Scendoni</name>
+ <organization>The Apache Software Foundation</organization>
+ <organizationUrl>http://www.apache.org/</organizationUrl>
+ <roles>
+ <role>committer</role>
+ </roles>
+ <url>http://people.apache.org/~anzelld/</url>
--- End diff --
...guess you'll need to change `anzelld` with your own ASF id, right?
> 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)
