Skip to content

chore: bump oauth2 gem to 2.0.12 to remove custom JWT Bearer Assertio…#44

Merged
mridang merged 1 commit into
mainfrom
chore/update-oauth2-version
Jun 2, 2025
Merged

chore: bump oauth2 gem to 2.0.12 to remove custom JWT Bearer Assertio…#44
mridang merged 1 commit into
mainfrom
chore/update-oauth2-version

Conversation

@mridang

@mridang mridang commented Jun 2, 2025

Copy link
Copy Markdown
Collaborator

Description
This pull request updates the oauth2 gem to version 2.0.12, which natively supports Key ID (kid) in JWT Bearer Assertions (RFC 7515). Previously, we applied a custom patch to the gem to implement this feature. The patch is no longer needed as it has been officially included in the latest release of the gem.

Related Issue
N/A. This PR is part of routine dependency updates.

Motivation and Context
This change is required to ensure the SDK is up-to-date with the latest version of the oauth2 gem. By updating to 2.0.12, we remove the need for our custom patch, leveraging the official support for Key ID (kid) in JWT Bearer Assertions, thus simplifying the implementation.

How Has This Been Tested?
The changes have been tested through the following automated steps:

  • SDK Generation: The generation script completed successfully without errors.
  • Linters and Formatters: The generated code passes all repository linting and formatting checks.
  • Continuous Integration (CI): The standard CI pipeline for this repository has been triggered, and all checks have passed.

Documentation
No changes to SDK-specific documentation are required, as the update does not introduce new API functionality.

Checklist:

  • I have updated the documentation accordingly. (Automated: Generator updates code-level documentation)
  • I have assigned the correct milestone or created one if non-existent.
  • I have correctly labeled this pull request. (Automated: 'sdk-generation', 'enhancement' labels applied)
  • I have linked the corresponding issue in this description. (Automated: N/A as per the "Related Issue" section)
  • I have requested a review from at least 2 reviewers.
  • I have checked the base branch of this pull request. (Automated: PR is targeted at the 'main' or 'develop' branch)
  • I have checked my code for any possible security vulnerabilities. (Automated: Generation is from a trusted upstream source; CI may include security scans)

@mridang mridang self-assigned this Jun 2, 2025
@mridang mridang added the enhancement New feature or request label Jun 2, 2025
@github-actions

github-actions Bot commented Jun 2, 2025

Copy link
Copy Markdown
Contributor

Qodana for PHP

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

@mridang mridang merged commit 42f7b17 into main Jun 2, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant