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?

[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.

[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?