With Fine Grained Authorization relation between MultiDatastream and Observation fails

[spezzi]

I'm using Fine Grained Authorization on a v. 2.4.6 FROST Server installation. I created a project (not public) and a user that I have associated to the project with the "read" role.
Then I have associated the project to the instances of the entities (Sensor, Thing, FoI and Location) that deals with it.
I tested many STA API endpoints with the user’s credential and everything seems ok, except when I try the relation between MultiDatastream and Observation and vice versa. For example, when I try

/FROST-Server/v1.1/MultiDatastreams(9)/Observations

I get an empty array and when I ask for

/FROST-Server/v1.1/Observations(44503)/MultiDatastream

I receive a “404 Not Found”.

If I make the same requests with the admin user, I get the right responses. No problems with the analogous relation between Datastream and Observation.

[infomehdi]

Having similar settings and the same problem, I noticed the SQL query used when fetching the observations is:

SELECT
  count(*)
FROM
  (
    SELECT
      "OBSERVATIONS"."PHENOMENON_TIME_START",
      "OBSERVATIONS"."PHENOMENON_TIME_END",
      "OBSERVATIONS"."RESULT_TIME",
      "OBSERVATIONS"."RESULT_NUMBER",
      "OBSERVATIONS"."RESULT_STRING",
      "OBSERVATIONS"."RESULT_QUALITY",
      "OBSERVATIONS"."VALID_TIME_START",
      "OBSERVATIONS"."VALID_TIME_END",
      "OBSERVATIONS"."PARAMETERS",
      "OBSERVATIONS"."RESULT_TYPE",
      "OBSERVATIONS"."RESULT_JSON",
      "OBSERVATIONS"."RESULT_BOOLEAN",
      "OBSERVATIONS"."ID",
      "OBSERVATIONS"."DATASTREAM_ID",
      "OBSERVATIONS"."FEATURE_ID",
      "OBSERVATIONS"."MULTI_DATASTREAM_ID"
    FROM
      "OBSERVATIONS"
    WHERE
      EXISTS (
        SELECT
          1
        FROM
          "OBSERVATIONS" AS "t"
          -- here ...
          JOIN "DATASTREAMS" AS "ds" ON (t."DATASTREAM_ID" = ds."ID")
          -- using MULTI_DATASTREAMS
          -- JOIN "MULTI_DATASTREAMS" AS "ds" ON (t."MULTI_DATASTREAM_ID" = ds."ID")
          -- would solve the problem
          JOIN "THINGS" AS "th" ON (ds."THING_ID" = th."ID")
          JOIN "THING_PROJECTS" AS "tp" ON (th."ID" = tp."THING_ID")
          JOIN "PROJECTS" AS "pr" ON (tp."PROJECT_ID" = pr."ID")
          LEFT OUTER JOIN "USER_PROJECT_ROLE" AS "upr" ON (pr."ID" = upr."PROJECT_ID")
          LEFT OUTER JOIN "USERS" AS "u" ON (upr."USER_NAME" = u."USER_NAME")
        WHERE
          (
            "OBSERVATIONS"."ID" = "t"."ID" AND ((
                pr."ISPUBLIC"
                AND NOT ds."RESTRICTED"
                AND NOT th."RESTRICTED"
              )
              OR u."USER_NAME" = '53bf5e29-b381-4c0c-8ad3-5038ccdb94a0'
            )
          )
      )
  ) AS "t"
WHERE
  "t"."ID" = 1

The problem is that it should have used JOIN "MULTI_DATASTREAMS" AS "ds" ON (t."MULTI_DATASTREAM_ID" = ds."ID") instead of JOIN "DATASTREAMS" AS "ds" ON (t."DATASTREAM_ID" = ds."ID"), in the case of MULTI_DATASTREAMS

[hylkevds]

You are right, MultiDatastream support in the Projects plugin is not quite complete yet.
The checks in secObservation.json only take Datastreams into account. We'll need a second version of that file that checks both the Datastream and MultiDatastream relation, and use that when the MultiDatastream plugin is active.