feat: Add guide for creating and authorizing sessions #36
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
docs/guides/govern/sessions.mdx
Outdated
| - Your server-side endpoint should apply some form of authorization logic to ensure that sessions are only granted access to tokens that should be accessible to the authenticated user. | ||
| - Follow the [principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege). In particular, try to only grant `token:read` or `token:use` access to specific tokens using [conditions](/docs/api/applications#access-rule-conditions), and avoid granting access to entire containers of tokens. | ||
|
|
||
| ## Read the Token |
There was a problem hiding this comment.
I'm standing up a working example service and FE components to test this code on Android and web. Once I have this finished, I want to add more to this section to show how to retrieve the token in Web/Android/iOS(?) - not only showing curl.
There is a tradeoff here, because we want to show how to use the session on each platform, not steer readers towards bad practices like retrieving raw plaintext data in the frontend, but also not dive into all of reveal elements here, especially since android and ios are not finished and I can't show them yet.
# [1.14.0](v1.13.0...v1.14.0) (2023-01-18) ### Features * Add guide for creating and authorizing sessions ([#36](#36)) ([b634a73](b634a73))
|
🎉 This PR is included in version 1.14.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Access Data Using SessionsguideAccess Controlsconcept pageRelevant preview links:
Guide
Concept page
Testing required outside of automated testing?
Screenshots (if appropriate):
Rollback / Rollforward Procedure
Reviewer Checklist