Add Drupal 11 support for 5x branch?

Created on 24 June 2025, 9 days ago

I have tried to get SimpleOauth 6.x working with Next.js and GraphQL Compose and I have had a hell of a time. Can we look at making an update to 5x to support Drupal 11?

✨ Feature request
Status

Active

Version

5.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States drupalninja99

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @drupalninja99
  • πŸ‡ΊπŸ‡ΈUnited States drupalninja99

    I have updated the branch here to support Drupal 11. https://git.drupalcode.org/issue/simple_oauth-3532181/-/tree/5.2.x. This is working for me as I try to upgrade DrupalX to 11x.

  • πŸ‡ΈπŸ‡ͺSweden enzipher

    Posting to add my voice to this. I'm working on a complex implementation where several features has been externally altered and I'd rather not resolve that in the upgrade process.

    Your issue fork seems to be working just fine. Thanks for sharing the work.

  • πŸ‡³πŸ‡±Netherlands bojan_dev

    Unfortunately it will be more work to maintain two versions with different architectures, also the other maintainers are no longer active. I rather not introduces any new features to 5.2.x or add D11 support, which would mean support will be extended.

    Perhaps you can explain your issue with Next.js, maybe I can help.

  • πŸ‡¨πŸ‡¦Canada pavlosdan

    The issue that we are facing (that may be different from others on this thread) is that for a fairly large headless implementation our FrontEnd apps have not implemented a way to refresh their access tokens. Upgrading to 6.x means we have to coordinate with multiple FE teams to redeploy at the same time as this upgrade goes live as it invalidates the access tokens.

    Having a D11 compatible 5.x version allows us to still go ahead with the D11 upgrade until our FE teams implement a way for themselves to refresh their access tokens.

  • πŸ‡ΊπŸ‡ΈUnited States drupalninja99

    @bojan_dev, I ran into too many issues, it wasn't just one isolated problem I could workaround or patch.

Production build 0.71.5 2024