You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something that's been discussed a bit in the past, and we're starting to see more adoption of, is expiring tokens in IndieAuth.
This would see an IndieAuth Resource Server, in this case the Micropub Server, returning HTTP 401 or HTTP 403s for bad authentication sent by the client, in the case that the token is no longer valid.
This would require handling these errors, and sending the user through a fresh authorization journey to receive new tokens.
As we're starting to see servers supporting this, it'd be good to have one of the more popular clients supporting this!
Something that's been discussed a bit in the past, and we're starting to see more adoption of, is expiring tokens in IndieAuth.
This would see an IndieAuth Resource Server, in this case the Micropub Server, returning HTTP 401 or HTTP 403s for bad authentication sent by the client, in the case that the token is no longer valid.
This would require handling these errors, and sending the user through a fresh authorization journey to receive new tokens.
As we're starting to see servers supporting this, it'd be good to have one of the more popular clients supporting this!
Related reading:
The text was updated successfully, but these errors were encountered: