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

INCIDEN-922: Restricting list client API action to specified user #897

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

Ryan-Andrews99
Copy link
Contributor

@Ryan-Andrews99 Ryan-Andrews99 commented Sep 10, 2024

Onboarding Feature Deployment

Warning

Pull requests merged to main will be released to production, please ensure the checklist below is complete

Before any work can be merged to main in must meet the definition of done and be ready to deploy. While many of these tasks will be automated, the reviewers must take the responsibility of confirming the checklist below has been completed before this ticket can be merged.

Checklist

  • this pull request meets the acceptance criteria of the ticket

  • this branch is up-to-date with the main branch

    git fetch --all && git rebase origin/main

  • these changes are backwards compatible (no breaking changes)

    • all methods signatures and return values are the same
    • any replaced methods are marked as @deprecated
  • tests have been written to cover any new or updated functionality

  • new configuration parameters have been deployed to all environments, see configuration management.

  • all external infrastructure dependencies have been updated in all environments

Changes

[ please list the changes this pull request is making ]

Added for new features

Changed for changes in existing functionality

Deprecated for soon-to-be removed features

Removed for now removed features

Fixed for any bug fixes:

  • Clients previously could view any user's service if they could navigate to it. This partially fixes the access control issue, meaning that the /get-service-client endpoint now has authorisation which checks for a User-Service relationship

Security in case of vulnerabilities

@Ryan-Andrews99 Ryan-Andrews99 force-pushed the inciden-922-enfore-access-token branch from 96914e0 to d1b3827 Compare September 10, 2024 13:47
@Ryan-Andrews99 Ryan-Andrews99 marked this pull request as ready for review September 10, 2024 13:47
@Ryan-Andrews99 Ryan-Andrews99 requested a review from a team as a code owner September 10, 2024 13:47
@Ryan-Andrews99 Ryan-Andrews99 force-pushed the inciden-922-enfore-access-token branch from d1b3827 to 99046dc Compare September 10, 2024 13:50
@Ryan-Andrews99 Ryan-Andrews99 changed the title INCIDEN-922: Restricting listClient API to specified user INCIDEN-922: Restricting API actions to specified user Sep 10, 2024
@Ryan-Andrews99 Ryan-Andrews99 force-pushed the inciden-922-enfore-access-token branch from f958309 to 6a1e9e3 Compare September 10, 2024 15:36
@Ryan-Andrews99 Ryan-Andrews99 force-pushed the inciden-922-enfore-access-token branch from 6a1e9e3 to 99046dc Compare September 11, 2024 13:25
@Ryan-Andrews99 Ryan-Andrews99 changed the title INCIDEN-922: Restricting API actions to specified user INCIDEN-922: Restricting list client API action to specified user Sep 11, 2024
We're now sending the access token from the frontend to the
backend, so we can now enforce some access control on listing
a client. This will restrict the user to only seeing the service
they created, so if they navigated to another user's service
the backend now returns a 403 - Forbidden
@Ryan-Andrews99 Ryan-Andrews99 added this pull request to the merge queue Sep 13, 2024
Merged via the queue into main with commit 3c69983 Sep 13, 2024
15 of 16 checks passed
@Ryan-Andrews99 Ryan-Andrews99 deleted the inciden-922-enfore-access-token branch September 13, 2024 14:50
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