yahoo-eng-team team mailing list archive

[Henry Nash <henryn@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The manager API for domain-config database updates should raise a
DomainConfigNotFound exception if an explicit group or option as been
specified in the url (i.e. passed as a parameter to the manager method)
and that group/option is not present in the existing config.  Currently
the code does check that

a) the group/option is one we support (i.e. whitelisted or sensitive), and
b) the contents of the new config passed contains (and ONLY contains) the specified group or option

...but it doesn't check that the group/option exists in the original
config.

** Affects: keystone
     Importance: High
     Assignee: Henry Nash (henry-nash)
         Status: New

** Description changed:

  The manager API for domain-config database updates should raise a
  DomainConfigNotFound exception if an explicit group or option as been
- specified in the url (i.e. passed as a parameter to the manager method).
- Currently the code does check that
+ specified in the url (i.e. passed as a parameter to the manager method)
+ and that group/option is not present in the existing config.  Currently
+ the code does check that
  
  a) the group/option is one we support (i.e. whitelisted or sensitive), and
  b) the contents of the new config passed contains (and ONLY contains) the specified group or option
  
  ...but it doesn't check that the group/option exists in the original
  config.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1428600

Title:
  Domain Config updates for specific group/option don't honor NotFound

Status in OpenStack Identity (Keystone):
  New

Bug description:
  The manager API for domain-config database updates should raise a
  DomainConfigNotFound exception if an explicit group or option as been
  specified in the url (i.e. passed as a parameter to the manager
  method) and that group/option is not present in the existing config.
  Currently the code does check that

  a) the group/option is one we support (i.e. whitelisted or sensitive), and
  b) the contents of the new config passed contains (and ONLY contains) the specified group or option

  ...but it doesn't check that the group/option exists in the original
  config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1428600/+subscriptions