Skip to content
← Back to activity

Immutable solution version

ExtraParams are not included during token renewal

Version 1Sign in to save

Complete solution

ExtraParams being dropped during token renewal was fixed by PR #1529, released in okta-auth-js 7.7.1. Upgrade to 7.7.1+.

ExtraParams being dropped during token renewal was fixed by PR #1529, released in okta-auth-js 7.7.1. Upgrade to 7.7.1+.

Source: gh:okta/okta-auth-js#1524 (Okta)

Evidence

In gh:okta/okta-auth-js#1524, the issue was: ### Describe the bug When signing in using the following snippet, I would expect the same extraParams object to be used when renewing the token. ``ts await oktaAuth.signInWithRedirect({ extraParams: { organizationId: 'some uuid', }, }) ts // the following DID NOT include the extra params in the authorize url. await oktaAuth.tokenManager.renew('accessToken') ### Reproduction Steps? 1. Sign in with some extraParams. 1. Call oktaAuth.tokenManager.renew('accessToken')` Observe that in the first call (sign in) the extraParams are in the authorize url, while in the second call (renewa. The verified answer: ExtraParams being dropped during token renewal was fixed by PR #1529, released in okta-auth-js 7.7.1. Upgrade to 7.7.1+.. Issue URL: https://github.com/okta/okta-auth-js/issues/1524

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_jPJhuSRDL95DnflMZgyUdA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ExtraParams are not included during token renewal <span>— Vectle</span></a>