You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by GitBox <gi...@apache.org> on 2019/09/26 04:27:42 UTC

[GitHub] [unomi] sergehuber edited a comment on issue #73: .identify() does not send events to dmp

sergehuber edited a comment on issue #73: .identify() does not send events to dmp
URL: https://github.com/apache/unomi/pull/73#issuecomment-535328040
 
 
   That's a very good question actually. I guess in this case the best thing is to be careful what kind of data you are storing in the profile to make sure that even if a merge happens no critical data can be retrieved. 
   
   I've been working on a way to "protect" properties that would only be accessible if a user is authentified but this is not yet available in Unomi.
   
   Also, if you use option 1 you could also not call the merge just to be on the safe side. A merge could happen only when a user is "truly" identified. Or you could check some request header that validates the request is coming through a known proxy or contains a key that would be difficult to retrieve publicly.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services