support arrays in custom JWT claims

Support for custom claims is great! But it chokes when we try to use an array –

code: “jwt-invalid-claims”
path: “$”
message: “x-hasura-* claims: expected Text, encountered Array”

Use case here is user “groups” (multiple). Not essential but including in the JWT would simplify our permission rules and save us some joins.

[Albert-Gao]

Need this feature,

otherwise, for a multi-tenant app, you might need to write Hasura Action for every query/mutation out there…

Any update on this?

In the documentation:

You can find this is allowed for x-hasura-allowed-roles:

{
  "sub": "1234567890",
  "name": "John Doe",
  "admin": true,
  "iat": 1516239022,
  "https://hasura.io/jwt/claims": {
    "x-hasura-allowed-roles": ["editor","user", "mod"],
    "x-hasura-default-role": "user",
    "x-hasura-user-id": "1234567890",
    "x-hasura-org-id": "123",
    "x-hasura-custom": "custom-value"
  }
}

So why we can not use it for the other claims?

Furthermore, the Postgres Array type is not a valid JSON format, one needs to manipulate JSON string to get it work. Not to mention, when work with AWS, which does not support JSON typed claims, so you have to pass a JSON string, and in that JSON string, we can only put a stringfied array there, like “{1,2,3}”, because otherwise, JSON.stringfy won’t even work., will this stringfied array still work?

[patrykwegrzyn]

Not sure if this helps I use something like this with nodejs , it will only works for the strings tho

function toPgArray(arr) {
  const m = arr.map(e=> `"${e}"`).join(",")
  return `{${m}}`
}

const ids = ["e63baafd-a10f-4d88-8828-0d423d698522"];
toPgArray(ids) 

results in

{
  "https://hasura.io/jwt/claims": {
  "sub": "1234567890",
  "name": "John Doe",
  "admin": true,
  "iat": 1516239022,
    "x-hasura-allowed-organisations": "{\"e63baafd-a10f-4d88-8828-0d423d698524\"}"
  }
}

the other solution would be to make proxy service that can convert arrays in claim to pg array format