Allow customization of `/auth/access-token` and `/auth/profile` URLs via `Auth0ClientOptions`

[spigelli]

Checklist

• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

My application utilizes HTTP rewrites to offer multi-tenant subdomains like in: https://vercel.com/templates/next.js/platforms-starter-kit

I'd like to configure access token and profile routes because I am instantiating tenant-specific Auth0Clients at request time based on the accessed subdomain

Describe the ideal solution

Instead of:

export type RoutesOptions = Partial<Pick<Routes, "login" | "callback" | "logout" | "backChannelLogout">>;

This:

export type RoutesOptions = Partial<Routes>;

Also update functions getAccessToken and useUser

Alternatives and current workarounds

No response

Additional context

No response

[tusharpandey13]

Hi @spigelli 👋

Thank you for opening this, I took a look at this and this seems like a reasonable enhancement that would enable more flexible route configuration patterns. We'll consider this for a future release.

Would you be interested in contributing a PR for this change? The main changes would be:

1. Update the RoutesOptions type definition
2. Update the functions that consume these routes (getAccessToken, useUser) to respect the programmatically configured routes
3. Update the documentation

Meanwhile, we have added this feature to our planning and will be working on this as well.