PART 1 of 2: When sending invites to multiple emails, the emails are populated into the To field, rather than Bcc. So everyone sees everyone else. This was addressed as a 'data breach' from client. Need to change this to Bcc to fix issue.
PART 2: https://github.com/hubzero/hubzero-cms/pull/1724
Brief summary of the fix
In the Email object, set the list of email to be sent Bcc (blind carbon copy) instead of To or Cc.
Screenshots showing fix
Before the change
After the change
Brief summary of your testing
Tried it on https://woo.aws.hubzero.org and once accepted, can push to stage.cmkc then production, bundle with other changes to push it out. Will need help from @nkissebe to do some grep's to find other instances of this.
Do the change needs to be hotfixed to any production hubs before a normal core rollout
Yes, it needs to be released because of client urgency.
Double check someone is assigned to review the ticket
Hi @nkissebe - tried removing and adding back setTo, but when I removed the setTo(), without it, I don't receive an email at all. But putting the setTo() back in, I do receive the email.
Source JIRA card(s) and hubzero ticket(s)
https://sdx-sdsc.atlassian.net/browse/USP-193
Brief summary of the issue
PART 1 of 2: When sending invites to multiple emails, the emails are populated into the To field, rather than Bcc. So everyone sees everyone else. This was addressed as a 'data breach' from client. Need to change this to Bcc to fix issue. PART 2: https://github.com/hubzero/hubzero-cms/pull/1724
Brief summary of the fix
In the Email object, set the list of email to be sent Bcc (blind carbon copy) instead of To or Cc.
Screenshots showing fix
Before the change
After the change
Brief summary of your testing
Tried it on https://woo.aws.hubzero.org and once accepted, can push to stage.cmkc then production, bundle with other changes to push it out. Will need help from @nkissebe to do some grep's to find other instances of this.
Do the change needs to be hotfixed to any production hubs before a normal core rollout
Yes, it needs to be released because of client urgency.
Double check someone is assigned to review the ticket
Yes - Nick and David