Url encoding of client_id and client_secret in fetching access token

[tychokamphuis-aqqo]

We have been provided with a client_secret which contain '=' signs, therefore giving "%3D" at the end when url encoded.
Our integration partner uses the original client_secret with = instead of %3D, therefore having an other basic authentication hash then we send to their side.

Is there a possibility for making the url_encode optional?

OpenID-Connect-PHP/src/OpenIDConnectClient.php

Line 1428 in 4f95102

$headers = ['Authorization: Basic ' . base64_encode(urlencode($clientId) . ':' . urlencode($clientSecret)),

[erkiha]

I second that. The same urlencode function messed up JWT claim verification in my case.