Bump firebase/php-jwt from 5.5.1 to 6.0.0

dependabot[bot] commented 1 year ago

Bumps firebase/php-jwt from 5.5.1 to 6.0.0.

Release notes

Sourced from firebase/php-jwt's releases.

v6.0.0

Note: This version is compatible with PHP >= 5.3

Backwards Compatibility Breaking Changes

The second argument of JWT::decode now must be Firebase\JWT\Key or array<string, Firebase\JWT\Key> (see #376)

The return type of Firebase\JWT\JWK::parseKey is now Firebase\JWT\Key (see #392)

The return type of Firebase\JWT\JWK::parseKeySet is now array<string, Firebase\JWT\Key> (see #376)

The "alg" parameter is required to be set for all JWKS parsed using Firebase\JWT\JWK::parseKeySet (see #376)

The flag JSON_UNESCAPED_SLASHES is now used for JSON decoding (see #376)

Constants ASN1_INTEGER, ASN1_SEQUENCE, and ASN1_BIT_STRING have been removed (see #376)

JWT::encode requires third argument $alg (see #377)

JWT::sign requires third argument $alg (see #377)

Using Firebase\JWT\Key

Using the Key object in JWT::decode

As a security fix, to avoid key type confusion (see #351), use of Firebase\JWT\Key is now required when decoding:
use Firebase\JWT\JWT;
// previous (v5.5.1 and below)
$decoded = JWT::decode($jwt, $publicKey, 'RS256');
// new (v6.0.0)
use Firebase\JWT\Key;
$decoded = JWT::decode($jwt, new Key($publicKey, 'RS256'));
Using the Key object in JWK::parseKey and JWK::parseKeySet

Calls to JWK::parseKey and JWK::parseKeySet now return a Key object and an array of Key objects respectively.
use Firebase\JWT\JWK;
// previous (v5.5.1 and below)
$key = JWK::parseKey($jwk); // $key is a resource
$keys = JWK::parseKeySet($jwks); // $keys is an associative array key ID to resources
// new (v6.0.0)
$key = JWK::parseKey($jwk); // $key is a Key object
$keys = JWK::parseKeySet($jwks); // $keys is an associative array of key ID to Key objects
If the keys in your JWKS do not contain the "alg", you need to set it manually to the expected algorithm, for it to be able to parse successfully:
</tr></table> 

... (truncated)

Changelog

Sourced from firebase/php-jwt's changelog.

6.0.0 / 2022-01-24

Backwards-Compatibility Breaking Changes: See the Release Notes for more information.

New Key object to prevent key/algorithm type confusion (#365)

Add JWK support (#273)

Add ES256 support (#256)

Add ES384 support (#324)

Add Ed25519 support (#343)

5.0.0 / 2017-06-26

Support RS384 and RS512. See #117. Thanks @joostfaassen!

Add an example for RS256 openssl. See #125. Thanks @akeeman!

Detect invalid Base64 encoding in signature. See #162. Thanks @psignoret!

Update JWT::verify to handle OpenSSL errors. See #159. Thanks @bshaffer!

Add array type hinting to decode method See #101. Thanks @hywak!

Add all JSON error types. See #110. Thanks @gbalduzzi!

Bugfix 'kid' not in given key list. See #129. Thanks @stampycode!

Miscellaneous cleanup, documentation and test fixes. See #107, #115, #160, #161, and #165. Thanks @akeeman, @chinedufn, and @bshaffer!

4.0.0 / 2016-07-17

Add support for late static binding. See #88 for details. Thanks to @chappy84!

Use static $timestamp instead of time() to improve unit testing. See #93 for details. Thanks to @josephmcdermott!

Fixes to exceptions classes. See #81 for details. Thanks to @Maks3w!

Fixes to PHPDoc. See #76 for details. Thanks to @akeeman!

3.0.0 / 2015-07-22

Minimum PHP version updated from 5.2.0 to 5.3.0.

Add \Firebase\JWT namespace. See #59 for details. Thanks to @Dashron!

Require a non-empty key to decode and verify a JWT. See #60 for details. Thanks to @sjones608!

Cleaner documentation blocks in the code. See #62 for details. Thanks to @johanderuijter!

2.2.0 / 2015-06-22

Add support for adding custom, optional JWT headers to JWT::encode(). See

... (truncated)

Commits

0541cba feat!: update return type for JWK methods (#392)
8699eb9 chore: update changelog for v6.0.0 (#391)
edda0f9 feat!: require Key object, use JSON_UNESCAPED_SLASHES, remove constants (#376)
fbe6394 chore(docs): fix typo in README
262f84c chore: switch main to master (#383)
12ec2fe chore(docs): add throws DomainException for JWT::decode (#379)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/owncloud/files_texteditor/network/alerts).

CLAassistant commented 1 year ago

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}