Nextjs get id token

[TharakaUJ]

Purpose

This PR introduces getIdToken API and exposes the following token-related APIs via the Next.js SDK context for parity with the React SDK:

• getDecodedIdToken
• getIdToken
• getAccessToken
• exchangeToken

This allows Next.js applications to access both raw and decoded tokens and perform token exchange using the same API surface as React.

Related Issues

• feat: expose the raw idToken from the SDK #249

Related PRs

• feat(react,nextjs): expose getIdToken API #309

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[TharakaUJ]

I haven't still test the code in action, I'll attach a screenshot once I'm done and open the PR.

[TharakaUJ]

The package is building fine now, but I noticed that the Next.js SDK has a separate server-side provider under packages/nextjs/src/server.

For now, to avoid build failures, I wired these methods through the existing client implementation.

I'm wondering whether I should follow the same pattern as in signIn, signOut etc. and create some implementation in packages/nextjs/src/server/actions.

@brionmario any advice?

[brionmario]

Hey @TharakaUJ,

Thanks a lot for the PR.

In the Next.js SDK, since we have a server side, token handling is done at the server level.
Have a look at https://github.com/asgardeo/javascript/blob/main/packages/nextjs/src/server/actions/getAccessToken.ts.
We can follow the same way.

[TharakaUJ]

I’ve made some updates to the last commit.

I adjusted the return types of a few interfaces to include undefined where necessary, to keep the types aligned and avoid inconsistencies.

For the server action APIs, I followed the same pattern used in getAccessToken.

Since the sessionPayload currently only contains accessToken and sessionId, retrieving the idToken and decodedIdToken directly from it wasn’t possible. Therefore, I used the client instance to obtain those values.

I’ve attached screenshots demonstrating how getAccessToken, getIdToken, and getDecodedIdToken are working.

I still need to verify the exchangeToken API behavior, I’ll update once that’s confirmed. In the meantime, please let me know if any changes are required.

Thank you!

[asgardeo-github-bot]

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.