You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2020/03/27 15:35:00 UTC
[jira] [Commented] (UNOMI-299) Revoking consent does not work if
there is a scope supplied when the consent was GRANTED
[ https://issues.apache.org/jira/browse/UNOMI-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068811#comment-17068811 ]
Serge Huber commented on UNOMI-299:
-----------------------------------
Yes you are right that is indeed a problem when a scope is present.
> Revoking consent does not work if there is a scope supplied when the consent was GRANTED
> ----------------------------------------------------------------------------------------
>
> Key: UNOMI-299
> URL: https://issues.apache.org/jira/browse/UNOMI-299
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.4.0
> Reporter: Ben Schiefer
> Priority: Major
>
> When GRANTING a consent, the consent is added to the consent object with a key of
> ```
> consent.getScope() + "/" + consent.getTypeIdentifier()
> ```
> When REVOKING a consent, only the typeIdentifier is used to find the key (see [https://github.com/apache/unomi/blob/ea1b788ec82b2ad8e404236e21d974a11e68429a/api/src/main/java/org/apache/unomi/api/Profile.java#L226])
>
> Expected Result:
> The profile.setConsent method should be consistent in using the same key for all consentStatuses.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)