bcprov-jdk18on and bcpkix-jdk18on to 1.86.https://example.com/r?a=1 produced a signature the
provider rejected. Signing a URI with a query string and signing the same
request with those parameters passed explicitly now agree. This affects
credentials, the request/access/refresh token exchanges, and xAuth, since
all of them route through base-string; a provider whose configured endpoint
carries a query string was failing the token exchange itself.+ in a query is decoded as a
space, matching application/x-www-form-urlencoded; a literal plus is still
expressible as %2B.ex-info errors containing
status, headers, body, and decoded OAuth error parameters.signed-request, plus signed GET, POST, PUT, and DELETE convenience
wrappers that generate OAuth parameters, Authorization headers, and execute
through clj-http.verify no longer double-encodes the token secret.form-decode splits each pair on the first = only, so padded base64 token
secrets are no longer truncated.net.clojars.savya/clj-oauth.Can you improve this documentation? These fine people already did:
Savyasachi & Savyasachi JagadeeshanEdit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |