should the `is` api be returning all decisions?

[shawnjones253]

topaz-node/src/authorizer/index.ts

Line 95 in 9cde450

const allowed = response.decisions[0]?.is;

^ this seems to indicate we should only be asking for one decision per call to is even though the parameters support an array of decisions -- this diverges from the response documented here and seems to indicate either:

1. the response should return all decisions
2. or, this implementation of is should only accept one decision rather than an array

[gertd]

This indeed looks incorrect to me. An Is call takes an IsRequest which contains a PolicyContext field that allows defining an array of decisions, in the same rule path.

The IsResponse message returns an array of decisions.

Using the Topaz PeopleFinder template as an example data and rule set:

grpcurl -insecure -d '{
  "policyContext": {
    "decisions": [
      "allowed",
      "visible",
      "enabled"
    ],
    "path": "peoplefinder.GET.api.users"
  },
  "identityContext": {
    "identity": "euang@acmecorp.com",
    "type": "IDENTITY_TYPE_SUB"
  }
}' localhost:8282 aserto.authorizer.v2.Authorizer.Is

returns

{
  "decisions": [
    {
      "decision": "allowed",
      "is": true
    },
    {
      "decision": "visible",
      "is": true
    },
    {
      "decision": "enabled",
      "is": true
    }
  ]
}

@gimmyxd can you please take a look at this?

[gimmyxd]

Sure, should be an easy fix.