Replacing xc-auth with xc-token #2909
Closed
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
Joffcom
added
community
|
Hey @valentina98, I have created #3073 which uses xc-token but also keeps xc-auth as an option for those still using the Swagger token this prevents a breaking change and also allows us to continue to have xc-auth on the off chance that NocoDB ends up adding more /user/ API endpoints that may be useful. I will mark this one as closed, If you have questions let me know and thanks for the PR 👍🏻 |
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.
The correct header for usage with an API key is xc-token.
The xc-auth is used only with expiring refresh tokens and it is unsustainable.