yahoo-eng-team team mailing list archive

[Sathianantha Thilagar <sathianantha.thilagar@xxxxxxxxx>]

Public bug reported:

Problem:

As part of the JSON body while creating user, the custom attribute/field
I added was used by keystone without causing any error/warning.

% curl -ik -X POST -H "X-AUTH-TOKEN: $token" -H "Content-Type: application/json" https://keystone:35357/v3/users -d '{"user": {"test_custom_field":"my value","name": "newuser"}}'
 HTTP/1.1 201 Created

The same custom attribute/field is accessible through curl GET while
openstack-client filters this attribute/filed while printing.

The setup version used here is Juno release.

Expected behavior:

HTTP 400

** Affects: keystone
     Importance: Undecided
         Status: New

** Summary changed:

- able to POST and GET custome attribute/field in JSON
+ able to POST and GET custom attribute/field in JSON

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

Title:
  able to POST and GET custom attribute/field in JSON

Status in OpenStack Identity (Keystone):
  New

Bug description:
  Problem:

  As part of the JSON body while creating user, the custom
  attribute/field I added was used by keystone without causing any
  error/warning.

  % curl -ik -X POST -H "X-AUTH-TOKEN: $token" -H "Content-Type: application/json" https://keystone:35357/v3/users -d '{"user": {"test_custom_field":"my value","name": "newuser"}}'
   HTTP/1.1 201 Created

  The same custom attribute/field is accessible through curl GET while
  openstack-client filters this attribute/filed while printing.

  The setup version used here is Juno release.

  Expected behavior:

  HTTP 400

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