syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SYNCOPE-880) Identity Recertification
Date Tue, 16 Aug 2016 07:25:20 GMT


ASF GitHub Bot commented on SYNCOPE-880:

Github user ilgrosso commented on a diff in the pull request:
    --- 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"
    --- End diff --
    Removing some production workflow looks fine, thanks.
    You might consider writing some sections about identity recertification in the [reference
guide](, also including some operational
notes as how to set assignment.

> Identity Recertification
> ------------------------
>                 Key: SYNCOPE-880
>                 URL:
>             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

View raw message