Hi Omindu,

Could you explain the need of this functionality with the view of the end
user?

Thanks,

On Sun, Jul 22, 2018 at 11:06 PM Omindu Rathnaweera <[email protected]> wrote:

> Hi All,
>
> As per the current implementation, we do not allow to edit or delete
> consent purposes which are associated with a consent receipt. The reason
> behind such a design decision was to preserve the immutability of the
> consent receipt. Meaning, to prevent modifying the existing consent
> receipts which are associated with purposes if a purpose is modified.
>
> However, with the improvements we are introducing with 5.7.0 privacy
> features, Self Signup and JIT functionalities will have a tight dependency
> on purposes and there will be more involvement around configuring purposes.
> The purposes defined for these scenarios cannot be modified once they are
> associated with a consent receipt.
>
> Therefore it would be convenient for the users to have the option to
> modify the existing consent purposes. But doing so should not change the
> existing consent receipts.
>
> In order to achieve this requirement. I see the following
>
> i) We can provide the capability to modify the existing purposes. For this
> we may have to duplicate the purposes when adding receipts and reference
> the duplicated purpose from the receipt.
>
> ii) Without providing the capability to modify the purposes, we can
> maintain a separate association of purposes and Self signup/JIT similar
> to what we are doing for service providers. This way a user can pick what
> purposes should be associated with a certain flow without modifying the
> existing purposes.
>
> Appreciate your thoughts on this.
>
> Regards,
> Omindu.
>
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>


-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: [email protected] <[email protected]>*
*Mobile: +94718566859*Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to