Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
Date: Thu, 11 Aug 2016 07:57:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@syncope.apache.org
Message-ID: <JIRA.12983338.1466966124000.280692.1470902240461@Atlassian.JIRA>
In-Reply-To: <JIRA.12983338.1466966124000@Atlassian.JIRA>
References: <JIRA.12983338.1466966124000@Atlassian.JIRA> <JIRA.12983338.1466966124735@arcas>
Subject: [jira] [Commented] (SYNCOPE-880) Identity Recertification
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 Aug 2016 07:57:22 -0000


    [ https://issues.apache.org/jira/browse/SYNCOPE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416719#comment-15416719 ] 

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_r74380625
  
    --- Diff: core/persistence-jpa/src/main/java/org/apache/syncope/core/persistence/jpa/entity/user/JPAUser.java ---
    @@ -184,6 +185,14 @@
         @Column(nullable = true)
         private String securityAnswer;
     
    +    @Column(nullable = true)
    +    private String lastRecertificator;
    +
    +    @Column(nullable = true)
    +    @Temporal(TemporalType.TIMESTAMP)
    +    private Date lastRecertificion;
    --- End diff --
    
    Fix spell `lastRecertification`


> 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)