Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for php-jwt 5 #210

Closed
deavial opened this issue Sep 30, 2017 · 7 comments
Closed

Support for php-jwt 5 #210

deavial opened this issue Sep 30, 2017 · 7 comments
Assignees
Milestone

Comments

@deavial
Copy link

deavial commented Sep 30, 2017

When will support for php-jwt 5 be coming? We have other composer plugins that require 5 and this is becoming an issue. google/apiclient has its dependency set to 4.0 || 5.0. Will an update be coming for this?

@cocojoe
Copy link
Member

cocojoe commented Oct 2, 2017

@victoriafrench This seems like an ideal update for 6.x (although there is no firm release date for this). I had a quick look and although it is a major, there is no mention of any breaking changes or migration requirements. Did you try setting 4.0 || 5.0 out of interest?

@deavial
Copy link
Author

deavial commented Oct 2, 2017

@cocojoe no we haven't tried yet. We are just now integrating the sdk in our site. That is the reason it came up as we were trying to figure out how to make things coexist together.

@anam-hossain
Copy link

@cocojoe Please bump php-jwt version to 5.0. I think, this will not break any feature.

@cocojoe
Copy link
Member

cocojoe commented Feb 9, 2018

@joshcanhelp can you take a look at this please, the min PHP for php-jwt 5.0 is 5.3 which is fine as our lib is min 5.5. It is however a major release so needs checked for any Breaking Changes in the API and tested.

@joshcanhelp
Copy link
Contributor

@cocojoe - I ran through the 5.0 release and nothing jumps out at me. Ran through the unit tests and everything related passed. Differences in the library are here:

firebase/php-jwt@v4.0.0...firebase:v5.0.0

Seems like the most likely candidate for issues is JWT::verify(), which we're not using at all.

@joshcanhelp joshcanhelp self-assigned this Feb 28, 2018
@joshcanhelp joshcanhelp added this to the v5-Next milestone Feb 28, 2018
@joshcanhelp
Copy link
Contributor

Fixed in v5.1.0

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants