Return-Path: <dev-return-11447-archive-asf-public=cust-asf.ponee.io@syncope.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 3C74A200B67
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 16 Aug 2016 09:25:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 3AFB3160A76; Tue, 16 Aug 2016 07:25:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 7A1E1160ABA
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 16 Aug 2016 09:25:21 +0200 (CEST)
Received: (qmail 10409 invoked by uid 500); 16 Aug 2016 07:25:20 -0000
Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@syncope.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@syncope.apache.org>
List-Post: <mailto:dev@syncope.apache.org>
List-Id: <dev.syncope.apache.org>
Reply-To: dev@syncope.apache.org
Delivered-To: mailing list dev@syncope.apache.org
Received: (qmail 10317 invoked by uid 99); 16 Aug 2016 07:25:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2016 07:25:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 8EC422C02A5
	for <dev@syncope.apache.org>; Tue, 16 Aug 2016 07:25:20 +0000 (UTC)
Date: Tue, 16 Aug 2016 07:25:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@syncope.apache.org
Message-ID: <JIRA.12983338.1466966124000.314197.1471332320581@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
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 16 Aug 2016 07:25:22 -0000


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

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_r74886819
  
    --- Diff: core/workflow-activiti/src/main/resources/userWorkflow.bpmn20.xml ---
    @@ -82,12 +82,47 @@ under the License.
         
         <serviceTask id="delete" name="Delete" activiti:expression="#{delete.execute(execution.processInstanceId)}"/>
         <sequenceFlow id="flow99" sourceRef="delete" targetRef="theEnd"/>
    +    <!-- Recertification tasks -->
    +    <userTask id="RecertificationRequest" name="Recertification Request" activiti:candidateGroups="managingDirector" activiti:formKey="recertify">
    --- End diff --
    
    Removing some production workflow looks fine, thanks.
    
    You might consider writing some sections about identity recertification in the [reference guide](https://ci.apache.org/projects/syncope/reference-guide.html), also including some operational notes as how to set assignment.


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