| Filename | Latest commit message | Latest commit date |
|---|---|---|
Per RFC 6749 section 6 and OAuth 2.1: when the server does not issue a new refresh_token on a refresh response, the client MUST keep the existing one. AuthorizationManager::refresh_token() was persisting the response verbatim, dropping the previous refresh_token and forcing full re-authorization on the next refresh. Match the fix from python-sdk#2270: preserve the existing refresh_token when the response omits it, replace when the server rotates. Fixes #921 Signed-off-by: SarthakB11 <sarthak.bhardwaj21b@iiitg.ac.in> |
||
| .. | ||
| rmcp | ||
| rmcp-macros | ||