60°F

Aaron Parecki

  • Articles
  • Notes
  • Photos
  • Aaron Parecki https://aaronparecki.com/   •   Aug 23
    The way I like to think about it is:

    If the client knows when the AT will (likely) expire, it can proactively refresh the token.

    There is nothing the client can do differently if it knows when the RT will (likely) expire.
    Aaron Parecki
    Yes, the client needs to be able to handle unexpected expiration of both the AT and RT, which tbh is more an argument that the AS should never return expires_in than an argument that it should return it for both tokens.
    Seattle, Washington, USA • 79°F
    Tue, Aug 23, 2022 4:49pm -07:00 #oauth
    1 like 1 reply
    • Fernando Fontoura
    • Fernando Fontoura twitter.com/fernandfontoura
      I agree! I think I have a partnership. :)
      Wed, Aug 24, 2022 12:09am +00:00 (via brid.gy)
Posted in /replies using quill.p3k.io

Hi, I'm Aaron Parecki, Director of Identity Standards at Okta, and co-founder of IndieWebCamp. I maintain oauth.net, write and consult about OAuth, and participate in the OAuth Working Group at the IETF. I also help people learn about video production and livestreaming. (detailed bio)

I've been tracking my location since 2008 and I wrote 100 songs in 100 days. I've spoken at conferences around the world about owning your data, OAuth, quantified self, and explained why R is a vowel. Read more.

  • Director of Identity Standards at Okta
  • IndieWebCamp Founder
  • OAuth WG Editor
  • OpenID Board Member

  • 🎥 YouTube Tutorials and Reviews
  • 🏠 We're building a triplex!
  • ⭐️ Life Stack
  • ⚙️ Home Automation
  • All
  • Articles
  • Bookmarks
  • Notes
  • Photos
  • Replies
  • Reviews
  • Trips
  • Videos
  • Contact
© 1999-2025 by Aaron Parecki. Powered by p3k. This site supports Webmention.
Except where otherwise noted, text content on this site is licensed under a Creative Commons Attribution 3.0 License.
IndieWebCamp Microformats Webmention W3C HTML5 Creative Commons
WeChat ID
aaronpk_tv