Skip to content

BB2-5374: Ensure mock relationships data is available when running lo… - #1806

Merged
JamesDemeryNava merged 3 commits into
masterfrom
jamesdemery/bb2-5374-mock-relationships-data
Nov 17, 2026
Merged

JamesDemeryNava merged 3 commits into
masterfrom
jamesdemery/bb2-5374-mock-relationships-data

Conversation

@JamesDemeryNava

Copy link
Copy Markdown
Contributor

…cally

JIRA Ticket:
BB2-5374

What Does This PR Do?

This PR adds mock data for the proxy relationships endpoint when running locally with auth=mock. This is so we can test proxy functionality locally without having to have actual proxy relationships set up in test.medicare.gov.

What Should Reviewers Watch For?

If you're reviewing this PR, please check for these things in particular:

  • Did I add the DJANGO_SLSX_RELATIONSHIPS_ENDPOINT var anywhere that it is not needed?

Validation

  • Pull down the branch, ensure you have the proxy_access waffle switch set to active
  • Set a breakpoint on line 220 in apps/dot_ext/views/authorization.py (the if at the top of get_context_data)
  • Run the debugger
  • Run make run-local auth=mock bfd=test
    • Go through a v3 auth flow (in testclient or postman). After clicking 'Sign In', the breakpoint you added will be hit. In the debugger view in VSCode, you should be able to click into self -> request -> session -> _session
    • There, you should see a user_relationships attribute which should have three records in it. Those will be the records shown in the app.py diff below.
    • Go through a v2 auth flow, confirm that the user_relationships value is just a blank list
  • Bring down the stack and run with auth=live. Confirm that the changes made here don't impact the v2 or v3 auth flow

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

  • Adds any new software dependencies
  • Modifies any security controls
  • Adds new transmission or storage of data
  • Any other changes that could possibly affect security?
  • Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
    security engineer's approval.

Any Migrations?

  • Yes, there are migrations
    • The migrations should be run PRIOR to the code being deployed
    • The migrations should be run AFTER the code is deployed
    • There is a more complicated migration plan (downtime,
      etc)
  • No migrations

@BenColeCode BenColeCode left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Works locally, looks good! The description of the PR starts with "...cally" so I do wonder if you typed something up somewhere else and then only got to paste some of it.

@JamesDemeryNava

Copy link
Copy Markdown
Contributor Author

Works locally, looks good! The description of the PR starts with "...cally" so I do wonder if you typed something up somewhere else and then only got to paste some of it.

I think that's just the title being log and bleeding into the description. Thanks for the quick turnaround on reviewing!

@JamesDemeryNava
JamesDemeryNava merged commit b310ae4 into master Nov 17, 2026
14 checks passed
@JamesDemeryNava
JamesDemeryNava deleted the jamesdemery/bb2-5374-mock-relationships-data branch November 17, 2026 14:06
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