-
Notifications
You must be signed in to change notification settings - Fork 16
Auth/PM-22661 - Send Access #351
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
base: main
Are you sure you want to change the base?
Conversation
…el + send access token struct
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #351 +/- ##
==========================================
+ Coverage 76.10% 76.73% +0.63%
==========================================
Files 264 268 +4
Lines 24045 24903 +858
==========================================
+ Hits 18299 19109 +810
- Misses 5746 5794 +48 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
… locations to be more idiomatic and logical
…flat structures and test utilities wiremock and zeroize.
…ng C dynamic lib, build a normal rust lib (rlib) for this crate since a C dynamic lib can't be used to run E2E tests.
…ion tests can only access the public API
…d request and grant errors
…n have output codes instead of sentences but we can still deserialize error descriptions from server.
…h optional error desc so we can make it truly optional in typescript
…and test everything.
…perly handle all known identity server responses + integrate our new, custom send_access_error_type enum for better handling instead of depending on a brittle, freeform error desc.
…pi_error_response changes.
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-22661
📔 Objective
To build out the SDK portion of the new
Auth/SendAccess
feature which serves outSendAccessTokens
for successful authN requests.⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes