dbGaP c999 Handling

Release Notes

For: uc-cdis/fence
Notes since tag: 4.8.0
Notes to tag/commit: eccddc1
Generated: 2019-10-22

New Features

• dbGaP sync supports handling "Common Exchange Area" user access via the
  c999 consent group now (#702)
• new configuration to turn on "granting Common Exchange Area user access via
  the c999 consent group" feature (#702)

Breaking Changes

• c999 is no longer converted to just phsid when parsing consent codes
  (which causes issues when switching the configuration on/off in terms of
  data access). Now, when consent code parsing is on, usersync handles c999
  by providing access to all consents explicitly (including itself,
  .c999, to represent the study-specific exchange area) (#702)

Deployment Changes

• Fence does NOT handle c999 the same as before. If using dbgap sync w/
  consent code parsing and indexd records have acls with just phsid to
  represent objects someone w/ c999 should be able to see, you will need to
  ensure that the records also have the phsid.consent_code as well or users
  will lose access (#702)
• Fence has a new configuration to support more dbGaP syncing options: if you
  require "Common Exchange Area" data access, review the new configuration
  and supply necessary values (#702)