Hi,
I found out that if the ClaimsIdentity was built using a different key name for name and role than ClaimTypes.Name and ClaimTypes.Role, the app under test can have problems if it is using ClaimPrincipal.IsInRole or ClaimPrincipal.Identity.Name. I think this can be solved if we pass those as options (ClaimInjectorHandlerOptions) so when creating the ClaimsPrincipal we pick these values. I'll create a PR later with the solution.
Hi,
I found out that if the ClaimsIdentity was built using a different key name for name and role than ClaimTypes.Name and ClaimTypes.Role, the app under test can have problems if it is using ClaimPrincipal.IsInRole or ClaimPrincipal.Identity.Name. I think this can be solved if we pass those as options (ClaimInjectorHandlerOptions) so when creating the ClaimsPrincipal we pick these values. I'll create a PR later with the solution.