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

Improve API error messages when using is_default field on taxonomy resources #5147

Merged
merged 5 commits into from
Jul 31, 2024

Conversation

NevilleS
Copy link
Contributor

@NevilleS NevilleS commented Jul 31, 2024

Description Of Changes

Today we throw a generic 403 error for a variety of edits which make it look like the user is lacking sufficient permissions, but in reality it is that they are forbidden from editing the is_default field on a resource (e.g. DataUse, DataCategory).

Current Error Message

For example, we had a user report this unexpected error: they called the /api/v1/data_category/upsert API with this body:

[
    {
        "version_added": "2.0.0",
        "is_default": true,
        "fides_key": "user.unique_id.my_custom_category",
        "organization_fides_key": "default_organization",
        "name": "custom data category",
        "description": "description for custom data category",
        "parent_key": "user.unique_id",
        "active": true
    }
]

Which returns this error:

{ 'detail': { 'error': 'user does not have permission to modify',
              'fides_key': 'user.unique_id.my_custom_category',
              'resource_type': 'DataCategory'}}

New Error Message

As you can see above, the message is confusing - the error actually isn't that the user is lacking permission, it's that the user is trying to create a resource with is_default: true, which we never allow.

With this change, the error looks like this instead:

{ 'detail': { 'error': "cannot create a resource where 'is_default' is true",
              'fides_key': 'user.unique_id.my_custom_category',
              'resource_type': 'DataCategory'}}

There are some slight variations on those messages for deleting/editing/etc.

Code Changes

  • Added a ForbiddenIsDefaultTaxonomyError error type with more user-friendly error messages
  • Updated test_api.py integration tests to assert on better error messages
  • Use the ForbiddenIsDefaultTaxonomyError error in the various code paths that were throwing generic 403s due to is_default rejections

Steps to Confirm

  • Run integration tests

Pre-Merge Checklist

  • All CI Pipelines Succeeded
  • Documentation:
    • [ ] documentation complete, PR opened in fidesdocs
    • [ ] documentation issue created in fidesdocs
    • [ ] if there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • Issue Requirements are Met
  • Relevant Follow-Up Issues Created
  • Update CHANGELOG.md
  • [ ] For API changes, the Postman collection has been updated
  • If there are any database migrations:
    • [ ] Ensure that your downrev is up to date with the latest revision on main
    • [ ] Ensure that your downgrade() migration is correct and works
      • [ ] If a downgrade migration is not possible for this change, please call this out in the PR description!

Copy link

vercel bot commented Jul 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
fides-plus-nightly ⬜️ Ignored (Inspect) Visit Preview Jul 31, 2024 6:48pm

Copy link

cypress bot commented Jul 31, 2024



Test summary

4 0 0 0


Run details

Project fides
Status Passed
Commit b12e8af0ff ℹ️
Started Jul 31, 2024 6:59 PM
Ended Jul 31, 2024 7:00 PM
Duration 00:36 💡
OS Linux Ubuntu -
Browser Electron 106

View run in Cypress Cloud ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Cloud

Copy link
Contributor Author

@NevilleS NevilleS left a comment

Choose a reason for hiding this comment

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

Quick self-review

detail = {
"error": "user does not have permission to modify",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was the main issue - this error message couldn't be overridden with anything more relevant to more specific types of 403 errors.

"resource_type": resource_type,
"fides_key": fides_key,
}
super().__init__(status.HTTP_403_FORBIDDEN, detail=detail)


class ForbiddenIsDefaultTaxonomyError(ForbiddenError):
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added this as an explicit way to encapsulate these types of "is default" logic errors and provide a more useful message.

self,
resource_type: str,
fides_key: str,
action: str = "modify",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This overcomplicates it a bit so that the error message says either "cannot modify", "cannot create", "cannot delete", etc.. I only did this as a bit of Python practice, to be honest.

error_message: str = None,
) -> None:
error = (
error_message or f"cannot {action} a resource where 'is_default' is true"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The error_message or <template string> allows providing an explicit error_message argument here. I use that in one place where the error is actually more subtle- we prevent the ability to modify is_default on a resource that already exists.

Comment on lines 2941 to 2942
print(f"result object: {result}")
print(f"result json: {result.json()}")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Doh, should have removed these. Going to wait for the tests to finish running in CI, then will delete.

Copy link
Contributor

@adamsachs adamsachs left a comment

Choose a reason for hiding this comment

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

lgtm! clean impl of a nice, targeted improvement 👍

error = (
error_message or f"cannot {action} a resource where 'is_default' is true"
)
super().__init__(
Copy link
Contributor

Choose a reason for hiding this comment

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

nice OOP :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK good, thanks. This was a bit of Python practice 👍

@NevilleS NevilleS merged commit e1ce0d1 into main Jul 31, 2024
13 of 14 checks passed
@NevilleS NevilleS deleted the ns-improve-is-default-error-messages branch July 31, 2024 18:48
Copy link

cypress bot commented Jul 31, 2024



Test summary

4 0 0 0


Run details

Project fides
Status Passed
Commit e1ce0d1
Started Jul 31, 2024 6:59 PM
Ended Jul 31, 2024 7:00 PM
Duration 00:37 💡
OS Linux Ubuntu -
Browser Electron 106

View run in Cypress Cloud ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Cloud

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.

2 participants