Skip to content

jimfuqian/BB2-3798 Node sample client to use SMART App v2 scopes #69

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

Merged
merged 6 commits into from
May 13, 2025

Conversation

JFU-NAVA-PBC
Copy link
Contributor

@JFU-NAVA-PBC JFU-NAVA-PBC commented Apr 14, 2025

JIRA Ticket:
BB2-3798
BB2-3802

Make necessary change to use SMART App v2 scope vs legacy scope.

What Does This PR Do?

Make necessary change to use SMART App v2 scope vs legacy scope.
(Append query parameter: scope=) to the authorize URL

What Should Reviewers Watch For?

  1. Verify the sample app works as expected
  2. Access token's scopes are SMART App v2 format

Validation

  1. Checkout this PR to local
  2. Configure the sample app as instructed by README: point to your app on SBX or TEST, note you need to add v2 scopes to your app (currently this is done through Django admin 'My application' view
  3. Start the sample app (docker compose up)
  4. Going through the authorization flow (medicare.gov login with synthetic user, grant data access permission e.g. share or not share demographic info etc.)
  5. Verify the access token is tied up with v2 scope vs legacy scope (this can be done by attaching to the sample app server component and put break point at the access token obtained line and exam the access token's scope
  6. OR on the bb2 server side check the access token (through django admin access token view)

@JFU-NAVA-PBC
Copy link
Contributor Author

JFU-NAVA-PBC commented Apr 30, 2025

Thanks for approval,

this PR will park here then sync with master after version bumps pr merged into master.
and then wait on PROD's coordination (should be in master after the API side ready for v2 scope consumption)

this PR will be merged to master ONLY when:

  1. node SDK v2 scope PR is in master AND
  2. node SDK v2 scope changes published to NPM

…ef to sdk version can only be set to 1.0.5 after bb2 node sdk 1.0.5 published
@JFU-NAVA-PBC JFU-NAVA-PBC merged commit 01d0edc into master May 13, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants