Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BREAK] The property "settings" is no longer available to regular users via rest api #10411

Merged
merged 1 commit into from
Apr 10, 2018

Conversation

graywolf336
Copy link
Contributor

@graywolf336 graywolf336 commented Apr 10, 2018

Closes #10401 - regular users won't see that property on the users endpoints anymore, but administrator users will.

Detail: After we added the property settings to the users, we forgot to include this property in our array of fields that should not go out to regular users except for when they view their own data via the rest api. The reason this is considered breaking is because we have removed a property that was added, so if you are expecting this property to be there it won't show up. Usually we deprecate these type of things, however, due to the privacy concerns we have immediately removed it.

Copy link
Member

@sampaiodiego sampaiodiego left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just change it to [BREAK]

@graywolf336 graywolf336 changed the title [FIX] Exposing users' "settings" to regular users via rest api [BREAK] The property "settings" is no longer available to regular users via rest api Apr 10, 2018
@graywolf336 graywolf336 merged commit b6b8b9e into develop Apr 10, 2018
@graywolf336 graywolf336 deleted the dont-expose-data branch April 10, 2018 23:16
trongthanh added a commit to goalifyplus/Goalify.Chat that referenced this pull request Apr 16, 2018
* goalify: (42 commits)
  Add Reload as global object
  update setup script domain to subdomain to setup S3 bucket
  [OTHER] Post to redhat registries api when tagging new release (RocketChat#10414)
  add setting Goalify API Gateway and Goalify API Token
  update initialSetting script to seed 1 time only
  Fix and improve vietnamese translation (RocketChat#10397)
  Don't expose the 'settings' property on users to regular users via the rest api (RocketChat#10411)
  [FIX] Updated OpenShift Template to take an Image as a Param (RocketChat#9946)
  Use Node 8.9 for CI build
  Fix incoming integrations being able to trigger a new message with a GET if there is no script enabled (RocketChat#9576)
  Update allowed labels by the rocket.cat gh bot (RocketChat#10360)
  [FIX] Snaps installations are breaking on avatar requests
  Update PULL_REQUEST_TEMPLATE.md
  Bump version to 0.64.0-develop
  Bump version to 0.63.1
  update dev apn key and cert
  Lower cased the first letter and removed unnecessary minus
  Fix: Incorrect French language usage for Disabled
  snap revert to 8.9.4
  Update saml_utils.js
  ...
@archang3l-media
Copy link

archang3l-media commented Apr 19, 2018

So this is a change for 0.64?
Just asking since it hasn't made it to 0.63.2 or 0.63.3 update and my organisation really needs the edit. Chances are high, I forget to edit the source myself after updating.

@kaiiiiiiiii
Copy link
Contributor

kaiiiiiiiii commented Apr 19, 2018

Yes, this is a change that will be included in the next release (PR is already merged).

@sampaiodiego sampaiodiego added this to the 0.64.0 milestone Apr 20, 2018
@rodrigok rodrigok mentioned this pull request Apr 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants