Skip to content

fix: Do not simply use bearer token from cookie for auth - #326

Merged
spencewenski merged 1 commit into
mainfrom
do-not-use-cookie-for-auth
Aug 12, 2024
Merged

spencewenski merged 1 commit into
mainfrom
do-not-use-cookie-for-auth

Conversation

@spencewenski

Copy link
Copy Markdown
Member

This approach is/may be vulnerable to a CSRF attack. More care/research is needed before taking this approach. For now, it's safer to simply use the authorization header.

This approach is/may be  vulnerable to a CSRF attack. More care/research
is needed before taking this approach. For now, it's safer to simply use
the authorization header.
@spencewenski
spencewenski merged commit ff48b19 into main Aug 12, 2024
@spencewenski
spencewenski deleted the do-not-use-cookie-for-auth branch August 12, 2024 00:53
@github-actions github-actions Bot mentioned this pull request Aug 12, 2024
spencewenski added a commit that referenced this pull request Aug 12, 2024
## 🤖 New release
* `roadster`: 0.5.18 -> 0.5.19

<details><summary><i><b>Changelog</b></i></summary><p>

<blockquote>

##
[0.5.19](roadster-v0.5.18...roadster-v0.5.19)
- 2024-08-12

### Added
- Redact bearer tokens in insta snapshots
([#325](#325))

### Fixed
- Do not simply use bearer token from cookie for auth
([#326](#326))
- Set default value for Jwt cookie name
([#324](#324))
- Derive `Clone` in JWT claim types
([#323](#323))
- Use `leptos_routes` in leptos example instead of
`leptos_routes_with_context`
([#322](#322))

### Other
- *(deps)* Bump EmbarkStudios/cargo-deny-action from 1 to 2
([#319](#319))
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/MarcoIeni/release-plz/).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Spencer Ferris <3319370+spencewenski@users.noreply.github.com>
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