Add revokeToken() function for client #739
Open
+242 −0
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Implement the revokeToken() function in the client library to allow clients to revoke tokens on the server.
Motivation and Context
The client library was missing OAuth token revocation functionality, which is essential for proper token lifecycle management and security best practices. While the server already supports token revocation (RFC 7009), clients had no way to programmatically revoke tokens during logout or cleanup scenarios.
This closes the gap in the OAuth implementation by providing client-side token revocation that integrates seamlessly with the existing OAuth client architecture.
How Has This Been Tested?
Breaking Changes
None. This is a purely additive change that doesn't modify any existing APIs or behavior.
Types of changes
Checklist
Additional context
None