Azure Static Web Apps: pass dynamic parameters to ./auth/login?

Hi @Tony Lunt
Apology for your inconveniences.
When using Azure Static Web Apps, dynamic parameters like login_hint are expected to be passed to the authentication provider via the URL during authentication. If the login_hint parameter is not making it through the redirects, this may be related to how Azure Static Web Apps manages the authentication process.

If your configuration does not specifically support preserving login_hint, the initial redirect to the login endpoint might drop this parameter. It's important to verify that your authentication provider is set up to accept and process login_hint. If adding login_hint manually to the final URL works, it suggests that Azure Static Web Apps is not retaining it throughout the authentication steps.

To resolve this, check that your authentication provider allows login_hint, review your Azure Static Web Apps authentication settings for anything affecting parameter forwarding, and consult Azure documentation or support for further guidance on this issue.
References:

• Custom authentication in Azure Static Web Apps
• Microsoft identity platform and OAuth 2.0 implicit grant flow
  If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please free to reach out to me.

@Shree Hima Bindu Maganti thank you again for all of your responses here. Based off everything you shared and the fact that my authentication provider supports login_hint, it appears that the Static Web App is dropping this parameter before the request forwards on to the authentication provider. I will open a support case with Azure.

UPDATE

I've tested with multiple users and looks like this approach does not work

----------------------------------------------

For those struggling with passing a login_hint to Azure Static Web App (SWA):

If swa is provisioned with the free hosting plan, you can neither customize aad flow nor enable login_hint due to a lack of azure app registration linked to the SWA.

When swa is created, a generic enterprise application is created with name Azure Static Web Apps for this and all other swas which handle built-in aad authentication.

To use login_hint, upgrade to standard hosting plan is required. After this a new app registration shall be created with:

1. a new client secret name and value and passed in the auth key of staticwebapp.config.json as explained here v4.hkg1.meaqua.org/en-us/azure/static-web-apps/authentication-custom.
2. In Token configuration -> Add optional claim login_hint

Now you can silently authenticate your user as this: https://app-url.com/.auth/login/aad?login_hint=******@site.com