[SDK-2405] Organisations support

[adamjmcgrath]

Description

Add support for Organisations (currently a Closed Beta)

• supports an organization config or AUTH0_ORGANIZATION environment variable which, when specified, passes the organization query param to the /authorize endpoint and validates it against the user's org_id ID Token claim.
• Allows the organization query param to be specified in the loginHandler and callbackHandler so that app's can support multiple Organzations.
• Document the invitation query parameter for the /authorize endpoint and add an example of creating a route that accepts Organization invites.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/auth0/nextjs-auth0/B5dKzs5isMrjRrufWbNzN3n72JtK
✅ Preview: Canceled

[Deployment for 0077fe7 canceled]

[stevehobbsdev]

🎉

[eluce2]

Can I see an example of this working? I've only implemented the basic configuration

// pages/api/auth/[...auth0].js
import { handleAuth } from "@auth0/nextjs-auth0";

export default handleAuth();

but when I call /api/auth/login?organization=orgId123 I get the following response:

invalid_request (parameter organization is required for this client)

And I can see from the auth0 logs that my query param was not passed through. What am I missing?

[adamjmcgrath]

Hi @eluce2

You can specify the AUTH0_ORGANIZATION=orgId123 environment variable or pass it as a custom option to handleLogin and handleCallback (see this example for passing custom authorization parameters https://github.com/auth0/nextjs-auth0/blob/main/EXAMPLES.md#customize-handlers-behavior)