# Day 3: Dev to Dev Hub High‑Five

**URL:** <https://community.auth0.com/t/day-3-dev-to-dev-hub-high-five/194510>\
**Category:** The 25 Days of Auth0 Community Daily Challenge\
**Created:** [December 3, 2025, 1:00pm UTC](https://community.auth0.com/t/day-3-dev-to-dev-hub-high-five/194510 "2025-12-03T13:00:45Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kazemi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/kazemi/32/56606_2.png) [@kazemi](https://community.auth0.com/u/kazemi)\
**Post date:** [December 3, 2025, 11:18pm UTC](https://community.auth0.com/t/day-3-dev-to-dev-hub-high-five/194510/3 "2025-12-03T23:18:40Z")

</div>

> [@Sessions and Refresh Tokens](https://community.auth0.com/t/sessions-and-refresh-tokens/194346):
>
> Hello developers! waving_handToday I am back to provide some insight in regards to how Auth0 Sessions work and some guides/information on Refresh Tokens and to correctly use them within specific SDKs or configurations on your Auth0 tenant. red_circle Sessions When talking about sessions within Auth0, we describe them as a group of interactions between a given user and the application they are using, regardless of the application type (SPA, Regular Web or Native). A user may have multiple se…

I really enjoyed this post by Nik on sessions and refresh tokens. It’s important to understand that there are different session layers and the responsibility a dev has when it comes to the application layer. In practice, it’s recommended to use short-lived tokens to shorten the window of opportunity for malicious users, but this introduces potential user friction since this means you have to re-authenticate more often. However, as Nik points out, refresh tokens (and token rotation) addresses this friction by allowing for silent authentication as long as the user’s IdP session is still valid.

---

_[View the full topic](https://community.auth0.com/t/day-3-dev-to-dev-hub-high-five/194510)._
