Error with Auth0 about headway

[grantcolley]

@VR-Architect The good thing is the issue is isolated to the WASM. If you haven't already checked the Auth0 logs, it may be worth seeing if they reveal anything useful.

[grantcolley]

@VR-Architect have you managed to get authentication for the WASM working?

Somebody posted a similar error on an Auth0 blog here, and the recommendation is basically check the Auth0 setup / WASM configuration. The poster doesn't appear to report back with their solution but I notice a couple of replies to the original post where others users experienced a similar issue and appeared to find different ways around it.

I tried messing around with my own Auth0 setup / WASM configuration but unfortunately I couldn't recreate it.

[VR-Architect]

I found an error on the Blazor Server which may be the root cause of the WASM also. I am not getting the email address in the claims from Auth0 which is causing the API to crash on start of debug. The claims I do get back show a scope of profile but not email. I agree with your assessment that I must have something not configured right in Auth0. Still looking. Thanks

[grantcolley]

The readme was missing the following step which I have now added.

Auth0 needs an Auth Pipeline Rule to return the email and role as a claim. I have added this to the readme.

function (user, context, callback) {
 	const accessTokenClaims = context.accessToken || {};
	const idTokenClaims = context.idToken || {};
  const assignedRoles = (context.authorization || {}).roles;
  accessTokenClaims['http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress'] = user.email;
  accessTokenClaims['http://schemas.microsoft.com/ws/2008/06/identity/claims/role'] = assignedRoles;
  idTokenClaims['http://schemas.microsoft.com/ws/2008/06/identity/claims/role'] = assignedRoles;
  return callback(null, user, context);
}