Fixed new 96 character access token fails validation.#654
Merged
danielmorell merged 1 commit intoApr 17, 2025
Merged
Conversation
danielmorell
deleted the
fixed/SDK-470-new-96-char-access-token-fails-validation
branch
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
2 participants
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.
Description of the change
This resolves an issue with the validation of our new 96 character access tokens. We were previously requireing access tokens be 32 characters long. This PR fixes that by allowing either a 32 character or 96 character token.
Type of change
Related issues
Checklists
Development
Code review