Closed (fixed)
Project:
Migrate Plus
Version:
6.0.x-dev
Component:
Plugins
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 May 2017 at 07:55 UTC
Updated:
15 Apr 2026 at 17:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pcambraThe yml settings would be like this:
Two subarrays with options, one for the provider, and another for the grants, such as user/password.
Comment #3
pcambraComment #4
pcambraSorry, a leftover :)
Comment #5
heddnThis would mean a bit of a BC break. What are the specific difficulties with one OAuth library vs another?
Comment #6
pcambraI understand that, however, the library is marked as optional and the proposed one is wildly more supported and more future proof. If you check the github stars it's quite clear which one is more popular and the oauth server library from the same vendor is the one used in simple_oauth which it's quite probable to make it to core eventually as part of the API first initiative.
My setup is a Drupal 7 with oauth2_server and I could not make the client credentials grant type work with the current one, I don't think it transforms the forms bit very well, whereas with the one proposed, everything worked as expected.
Comment #7
heddnI think I'm ok with the swap but I'd like to hear input from mikeryan.
Comment #8
heddnI'm leaning towards accepting this approach. However, I'd like to see some tests. And docs on how to implement this. Perhaps in the doxygen of OAuth2
Comment #9
heddnI checked with @mikeryan and he's also OK with swapping out libraries. Only missing some simple tests and docs.
Comment #10
jon nunan commentedRe-roll for 8.x-5.x
Comment #11
heddnI don't think we can just replace this. We'll need to add it as a second plugin. Otherwise, we'd break existing sites.
Can we do that, and upload the results to the duplicate issue on gitlab: https://gitlab.com/drupalspoons/migrate_plus/-/issues/186
Comment #12
krisahil commentedRe-rolled against 6.0.x branch.
Comment #13
dbrowncode commentedComment #14
krisahil commentedHere's a patch that applies to releases 6.0.9 and 6.0.10.
Comment #15
heddnCan we add this as a MR?
Comment #16
krisahil commentedComment #19
jsacksick commentedBumping the priority because I'm currently unable to update my project due to the sainsburys/guzzle-oauth2-plugin library requiring firebase/php-jwt ~3.0 which is affected by a security advisory:
Comment #20
jsacksick commentedDisregard my previous message... I had another composer.json included from a custom module requiring the same library... So this wasn't coming from Migrate plus.
Comment #21
herved commented#19 Same here! That SA just popped up today I believe.
I need firebase/php-jwt > 7.0 but sainsburys/guzzle-oauth2-plugin v3.0.7 requires firebase/php-jwt (^3.0|^4.0|^5.0|^6.0).
sainsburys/guzzle-oauth2-plugin doesn't seem maintained anymore and at the moment the oauth2 plugin here relies on it. So this is major IMO.
Comment #22
herved commented#11 Do we really want to maintain the old plugin which relies on an insecure package? and if so, how to name the new plugin?
Edit: I'll create a different MR with a new plugin named oauth2_client (?), and mark the old plugin as deprecated.
Comment #24
herved commentedStatic patch from MR156
Comment #26
herved commentedComment #27
heddnPosted some comments on the MR.
Comment #28
heddnThis is look pretty nice. About to merge.
Comment #29
heddnChange record published and code merged.