The user experience is that data flow is not interrupted. If I get a notification in advance, I can re-authorize before the original grant expires. Then, on the server side, there's no need to fetch any "missed" data from when the original grant expired.
I see this as a subscription without auto-pay -- rather than waiting for my renewal date and pausing my subscription until I pay, it's nice if the service notifies me that it's about to expire. As the service provider, there's no need to interrupt the service if the user renews in time. Vanshaj On Fri, Nov 14, 2025 at 07:51 Neil Madden <[email protected]> wrote: > > > > On 14 Nov 2025, at 15:14, Max Gerber <[email protected]> wrote: > > > > > […] The client can also schedule a notification to the user to renew > the grant in 11 months. > > But what does this mean in practice? Asking them to re-login and > re-approve the scopes? If so, why not just wait for the grant to expire and > do that anyway? What is the concrete benefit to user or developer > experience of this field? > > — Neil > _______________________________________________ > OAuth mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
