Skip to content

Update project to query access tokens using the client assertion mechanism - #18

Merged
clement911 merged 5 commits into
mainfrom
feat/request-clientassertion-accesstoken
Nov 3, 2026
Merged

clement911 merged 5 commits into
mainfrom
feat/request-clientassertion-accesstoken

Conversation

@matnun-br

Copy link
Copy Markdown
Contributor

No description provided.

… mechanism rather than relying on a static value which expires. All parameters are provided via environment variables

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the switch to client-assertion authentication.

No open issues 🎉

What changed in this PR

This PR switches the type generator and integration tests from a configured shop token to access tokens obtained through client assertion authentication.

Changes:

  • Request access tokens using the client ID, key ID, and private key.
  • Acquire one token during client-test class initialization and use fixed credentials for mocked token-bucket tests.
  • Replace the shop-token secret in CI with client assertion credentials.
File Description
ShopifyNet.TypeGenerator/​TypeGenerator.cs Requests an access token and validates required environment variables.
ShopifyNet.Tests/​TokenBucket/​TokenBucketInterceptorTests.cs Separates mocked credentials from live-test token acquisition.
ShopifyNet.Tests/​TestHelper.cs Adds credential accessors and a shared token-request helper.
ShopifyNet.Tests/​ShopifyClientTests.cs Obtains an access token during class initialization.
.github/​workflows/​ci.yml Supplies client assertion secrets to the test step.

Review effort: Balanced

@clement911
clement911 merged commit 05b42c9 into main Nov 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants