User access token refresh and reset should be more consistent

[xmo-odoo]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Apps

Body

This would be especially useful now that oauth apps have been updated to support expiring tokens

reset

Resetting a token returns a lot of authorization metadata, but even though it looks useful it's useless for expiring UATs because it doesn't bump the expires_at, it just updates the token (and updated_at) on the installation. So this endpoint is only useful to force the rotation of non-expiring user access tokens, if you're using expiring tokens (which is clearly the future as far as github is concerned) you might as well refresh the token immediately.

Resetting a token should either bump the expires_at (it still requires a valid UAT anyway, and does not affect the refresh_token), or be clearly documented as useless / deprecated for expiring UATs.

refresh

Refreshing a token does bump expires_at, and rotates the refresh_token, however unlike reset it only returns the lifetime of the two values, it doesn't return the actual expiry times. This makes the expiry information a lot less convenient in many cases as the caller has to process expires_in and refresh_token_expires_in quickly, and is more constrained on its clock drift wrt github.

Even though that is not part of the oauth standard for some fool reason, it would be really nice if github could return the expires_at and refresh_token_expires_at values when refreshing a token.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐