URL encode client id as per OAuth 2.0 RFC 6749 Section 2.3.1#716
Merged
URL encode client id as per OAuth 2.0 RFC 6749 Section 2.3.1#716
Conversation
Closed
|
Thank you! |
acoburn
approved these changes
Dec 8, 2025
|
Given #673 I'm currently not trying to build image from this branch. Once this PR is merged and new OCI image is published I will try to add it to my https://dagger.io/ based testing setup in https://sai.js.org and write common Karate DLS tests instead of writing vitest suite only useful for my implementation. I find dagger based setup pretty useful to run the same tests locally and on any CI, I could see if it can be generalized to make it even easier for any implementation to test conformance with this harness. |
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
3 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.
This is the change from #661 written by @elf-pavlik