feat: Support for bearer token authentication and no authentication and PUT method in REST calls #803
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…for organisation apis (#797) * Handling null pointers when meta info is null in a response * Add fetcher class under noauth package * Making token fetch thread safe * Token re fetch logic implementation * adding token class files
…earer token auth and Support for PUT method (#802) * Docs update for bearer token authentication and endpoints with no auth * Support for put request in clients
|
sbansla
approved these changes
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes
A short description of what this PR does.
Support for bearer token authentication and no authentication and PUT method in REST calls
Checklist
If you have questions, please file a support ticket, or create a GitHub Issue in this repository.