[ ] Introduce claims_map in JWT configuration that allows you to use JWT tokens without any custom Hasura claims see here section claims_map
[x] it looks like unique_name claim is sometimes simply called "name"
see aspnet/Security#1910 maybe add the following to CreateJWT and CreateJWTMiddlewareServer: JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear()
this leads to failed tests and maybe also to our current issue with login for lxd hosts
@tpurschke would you take care of the custom Hasura claim mapping so we can get rid of the additonal x-hasura-... claims?
You can then again assign me the issue so i can take care of the c# part
[ ] Introduce claims_map in JWT configuration that allows you to use JWT tokens without any custom Hasura claims see here section claims_map
[x] it looks like unique_name claim is sometimes simply called "name" see aspnet/Security#1910 maybe add the following to CreateJWT and CreateJWTMiddlewareServer: JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear() this leads to failed tests and maybe also to our current issue with login for lxd hosts