Auth0 Invitation Parameter Fails in PAR and JAR Flows

When using Pushed Authorization Requests (PAR) or JWT Secured Authorization Requests (JAR) flows in Auth0, users land on the login page instead of the create password screen. This occurs because Auth0 does not support the invitation and screen_hint parameters in these flows and strips them during parsing. Resolve this by using the standard /authorize endpoint for initial sign-ups or by enabling the Auto-Membership feature.

• Auth0
• Pushed Authorization Requests (PAR)
• JWT Secured Authorization Requests (JAR)
• Organization Invitations

Auth0 does not support the invitation and screen_hint parameters in PAR and JAR flows. Auth0 strictly enforces accepted parameters in these flows and ignores any unsupported parameters passed to the /authorize endpoint, stripping them out during the parsing stage. Additionally, while the organization parameter functions during standard authentication, it fails during invitation flows due to this same limitation.

How does Auth0 handle organization invitations with PAR and JAR?

Currently, Auth0 lacks a native method to execute the organization invitation flow through PAR or JAR.

What are the workarounds for the unsupported invitation parameters?

Resolve the unsupported parameter limitation by either routing the initial sign-up through the standard authorization endpoint or by enabling the Auto-Membership feature on the organization.

• Use the standard /authorize endpoint for the initial sign-up flow, and then switch to PAR or JAR for subsequent authentication requests.
• Enable Auto-Membership on the organization. NOTE: Evaluate the operational implications before enabling this feature.