User Profile

Posts

Posts

Post not yet marked as solved
17 Replies
Replied In invalid_client for authorization_code
That is incorrect and not the cause of the problem, the signature is valid.
Post not yet marked as solved
17 Replies
Replied In invalid_client for authorization_code
The firebase/php-jwt library uses PHP's native `openssl_sign()` function to generate the signature. To my understanding, ES256 uses SHA256 as well, but places ES256 in the header of the signature.Please note that the generated signature does get validated in the JWT.io debugger, so there seems nothing wrong with the signature itself.
Post not yet marked as solved
17 Replies
Replied In invalid_client for authorization_code
Thank you, I was already aware of that. The library will throw an error and never reach the point of the `invalid_client` response from Apple. In order to use ES256 with the Firebase php-jwt library, I extend the class and override the array of supported methods:namespace my\namespace; class JWT extends \Firebase\JWT\JWT { public static $supported_algs = [ 'ES256' => ['openssl', 'SHA256'], 'HS256' => ['hash_hmac', 'SHA256'], 'HS512' => ['hash_hmac', 'SHA512'], 'HS384' => ['hash_hmac', 'SHA384'], 'RS256' => ['openssl', 'SHA256'], 'RS384' => ['openssl', 'SHA384'], 'RS512' => ['openssl', 'SHA512'], ]; }
Post not yet marked as solved
17 Replies
Replied In invalid_client for authorization_code
Unfortunately, nothing yet.
Post not yet marked as solved
17 Replies
Replied In invalid_client for authorization_code
Thank you for your reply. With Radar I think you mean the Feedback Assistant? I just submitted an entry with ID FB7219694.