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

Add Permissions integration tests #1550

Merged
merged 4 commits into from
Sep 18, 2024
Merged

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented Sep 13, 2024

Feature or Bugfix

  • Feature: testing

Detail

Implement tests for Permissions api calls (inside core/permissions) as part of #1220

!Excludes updateSSMParameter mutation - I think it is unused

Relates

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Comment on lines +29 to +30
admin_group = next(group for group in response.nodes if group.groupUri == 'DHAdmins')
assert_that(admin_group).contains_key('tenantPermissions')
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: any reason we filter for DHAdmins and not just take the first entry like response.nodes[0] to ensure it contains tenantPermissions key?

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 DHAdmins is a group created during deployment; it is the only one with the tenant permissions. It is true this is testing something else. We could break it down into 2 tests - test_tenant_group_exists and test_list_tenant_groups

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I ended up adding a comment to explain the purpose of that last check

Copy link
Contributor

Choose a reason for hiding this comment

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

okay I think makes sense - may be no need to include response.nodes[0] since it is duplicate chck of admin_group which is testing the same and more, but PR looks good

Copy link
Contributor

@noah-paige noah-paige left a comment

Choose a reason for hiding this comment

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

Left one minor nit but this PR looks good and tested for checks passing

@dlpzx dlpzx merged commit 1570ed3 into main Sep 18, 2024
9 checks passed
@dlpzx dlpzx deleted the feat/integration-tests-permissions branch September 19, 2024 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants