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

WIP: [Feat] Jwt #1178

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

WIP: [Feat] Jwt #1178

wants to merge 3 commits into from

Conversation

shepherd-l
Copy link
Contributor

@shepherd-l shepherd-l commented Jun 4, 2024

Description

1 Line Summary

WIP for adding Jwt identity verification

Details

Systems Affected

  • WebSDK
  • Backend
  • Dashboard

Validation

Tests

Info

Checklist

  • All the automated tests pass or I explained why that is not possible
  • I have personally tested this on my machine or explained why that is not possible
  • I have included test coverage for these changes or explained why they are not needed

Programming Checklist
Interfaces:

  • Don't use default export
  • New interfaces are in model files

Functions:

  • Don't use default export
  • All function signatures have return types
  • Helpers should not access any data but rather be given the data to operate on.

Typescript:

  • No Typescript warnings
  • Avoid silencing null/undefined warnings with the exclamation point

Other:

  • Iteration: refrain from using elem of array syntax. Prefer forEach or use map
  • Avoid using global OneSignal accessor for context if possible. Instead, we can pass it to function/constructor so that we don't call OneSignal.context

Screenshots

Info

Checklist

  • I have included screenshots/recordings of the intended results or explained why they are not needed

Related Tickets



This change is Reviewable

@shepherd-l shepherd-l force-pushed the feat/jwt branch 4 times, most recently from db72ea5 to 005e3dd Compare June 6, 2024 18:36
Adds jwtToken as a property of OSModel. Removes unused jwtTokenAvailable property from Operation. Removes storing jwtToken in the Database. Since jwtToken is on OSModel, operations can access it from Operation.model.jwtToken and it doesn't need a separate property on Operation.
Removed APIHeaders type as RequestMetadata can be used to create the Jwt header instead. Moved callers passing subscriptionId as a separate parameter and including it in their RequestMetadata parameter instead to utilize RequestMetadata's subscriptionId property (furthering implementation of e5c2a10). Future consideration: add AliasPair to RequestMetadata. Additionally, renamed parameters and method name in OneSignalApiBase for more clarity
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.

1 participant