4.1 caused ruby integration to break

  • Resolved scmsteve

    (@scmsteve)


    5 years, 6 months ago

    Unsure what exactly is going on, but after upgrading to 4.1.3 (first in the 4.1 series we saw to upgrade to) our integration with a ruby app has broken. This app was developed by a third party so I do not have all the particulars, but they were getting this strange message:

    OAuth2::Error, invalid_grant: Authorization code doesn’t exist or is invalid for the client
    {“error”:”invalid_grant”,”error_description”:”Authorization code doesn’t exist or is invalid for the client”}

    Rolling the plugin back to 4.0.2 resolved the problem and the site is operational again.

    What in the 4.1 upgrade would require changes to external apps? Is the addition of PKCE now a requirement that has to be implemented in the client? I don’t know all the moving pieces, just trying to find out why the upgrade broke things and how to fix it going forward.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Justin Greer

    (@justingreerbbi)

    5 years, 6 months ago

    Thank you for posting, and I am sorry you are experiencing these issues. We have tracked down the issue and cause.

    A solution is that after updating the plugin, manually deactivate and reactivate the plugin. This will for sure trigger the update script for the database.

    We are working on a fix and update now.

    Plugin Author Justin Greer

    (@justingreerbbi)

    5 years, 6 months ago

    We have updated the plugin and it contains the fix to this issue. Please update to at least 4.1.5 ASAP.

    For reference, PKCE is not required.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘4.1 caused ruby integration to break’ is closed to new replies.