Closed mr-blue-sky closed 6 days ago
Hail, @mr-blue-sky 👋 Welcome to Fief's kingdom!
Our team will get back to you very soon to help.
In the meantime, take a minute to star our repository ⭐️
Subscribe to one of our paid plan to help us continue our work and receive exclusive information and benefits! Starts at $5/month 🪙
Farewell!Hi!
Actually, we already support refresh tokens. All you need is to ask for the offline_access
scope when authenticating user. Admittedly, this may not be very well documented 😅
Hello Fief team,
First, I want to thank you for creating and maintaining such an excellent open-source authentication and user management platform. Fief has been instrumental in managing our user authentication and authorization needs, and we appreciate the comprehensive documentation and support provided.
Currently, Fief supports access tokens for JWT-based authentication, which works seamlessly for many use cases. However, we've encountered scenarios where the addition of refresh tokens would significantly enhance the security and usability of our applications. Specifically, we are developing a mobile application where the following features of refresh tokens are crucial:
I understand from the project roadmap that Fief is continuously evolving with many exciting features planned for the future. Could you please provide some insight into whether there are plans to implement refresh tokens? If so, is there an estimated timeline for this feature?
Additionally, if this feature is not currently planned, could you share any potential challenges or considerations that need to be addressed to include refresh token support? Understanding these aspects might help the community contribute effectively towards this enhancement.
Thank you for your time and consideration.
Best regards :)