cognitoauth: Fix "Unexpected char 0x0a at 82 in header value" Error When Using Client Secret #327
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 request fixes issue #315, which occurs whenever a client secret is used.
Pkce.encodeBase64() currently uses Base64.DEFAULT when creating the base64-encoded string to be used for the PKCE Authorization header. This breaks the ability to use a client secret, as Base64.DEFAULT adds a newline (0x0a) character at the end of the encoded string, which results in the call to httpsURLConnection.addRequestProperty() in AuthHttpClient.httpPost() to throw an exception with a stack trace similar to the following: