fix: make token type comparison case-insensitive in authentication#77
Merged
PatrickE94 merged 1 commit intomainfrom Nov 4, 2025
Merged
fix: make token type comparison case-insensitive in authentication#77PatrickE94 merged 1 commit intomainfrom
PatrickE94 merged 1 commit intomainfrom
Conversation
The Zaptec API returns token_type as "bearer" (lowercase), but the code was checking for exactly "Bearer" (uppercase), causing authentication to fail. Changed the comparison to be case-insensitive using toLowerCase(). Also fixed the error message which was incorrectly showing data.token_type twice instead of displaying the expected value "Bearer".
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 Zaptec API returns token_type as "bearer" (lowercase), but the code was checking for exactly "Bearer" (uppercase), causing authentication to fail. Changed the comparison to be case-insensitive using toLowerCase(). This is likely due to an API update. We now ignore casing in our comparison.
Also fixed the error message which was incorrectly showing data.token_type twice instead of displaying the expected value "Bearer".