Skip to content

fix(cc-widgets): update cc sdk version for the invalid_access_token - #758

Open
akulakum wants to merge 3 commits into
webex:nextfrom
akulakum:FIX_INVALID_ACCESS_TOKEN_401_AND_403
Open

akulakum wants to merge 3 commits into
webex:nextfrom
akulakum:FIX_INVALID_ACCESS_TOKEN_401_AND_403

Conversation

@akulakum

@akulakum akulakum commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

COMPLETES https://jira-eng-sjc12.cisco.com/jira/browse/CAI-8643

SDK pull request: webex/webex-js-sdk#5275

Vidcast link: https://app.vidcast.io/share/4735574a-ba84-4213-9fd4-68f2a9ffe823

This pull request addresses

When an invalid access token is still in the session, the postauth service catalog returns HTTP 401 or 403. The SDK used to hide that status, so the widget saw service-interceptor: 'wcc-api-gateway' is not a known service.

The SDK fix is merged. This pull request picks up that SDK in the Contact Center widget.

by making the following changes

  • @webex/contact-center in the Contact Center store moves from 3.12.0-next.159 to 3.13.0-next.9.
  • webex in the Contact Center React sample moves from 3.12.0-next.249 to 3.13.0-next.14.
  • yarn.lock is updated for those versions.

Both packages are published from SDK commit b124d984, the merge of the SDK pull request above. They depend on @webex/webex-core 3.13.0-next.5.

A catalog 401 is now invalid_access_token with statusCode 401. A catalog 403 is access_denied with statusCode 403. This SDK change does not clear the access token.

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • The testing is done with the amplify link

The SDK behavior was verified before the SDK pull request was merged. A catalog 401 shows Error: invalid_access_token on Register. A catalog 403 shows Error: access_denied. This widget change is the version bump that consumes that SDK.

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify: Cursor
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

Checklist before merging

  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the testing document
  • I have tested the functionality with amplify link

@akulakum
akulakum requested a review from a team as a code owner November 13, 2026 08:54
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-13T11:56:38.270451Z b6623df New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ff53563215

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

},
"dependencies": {
"@webex/contact-center": "3.12.0-next.159",
"@webex/contact-center": "3.13.0-next.9",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update the module spec with the new SDK pins

The dependency pins change here and in the React sample, but packages/contact-center/store/ai-docs/store-spec.md:539-544 still explicitly identifies @webex/contact-center 3.12.0-next.159 and webex 3.12.0-next.249 as the installed pair; its Stack and Requires sections also retain the old SDK pin. This violates the root AGENTS.md Spec-currency rule and leaves the documented SDK compatibility baseline inconsistent with the manifests. Update the module spec’s current-version declarations and any affected compatibility guidance in this same change.

AGENTS.md reference: AGENTS.md:L68-L68

Useful? React with 👍 / 👎.

@aws-amplify-us-east-2

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-758.d1b38q61t1z947.amplifyapp.com

@akulakum akulakum added the validated Indicates that the PR is ready for actions label Nov 13, 2026
@github-actions github-actions Bot removed the validated Indicates that the PR is ready for actions label Nov 13, 2026
@akulakum akulakum added the validated Indicates that the PR is ready for actions label Nov 13, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated Indicates that the PR is ready for actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants