Mailing-List: contact users-help@isis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@isis.apache.org
Message-ID: <5a1ff241.8b6e240a.ec36c.e905@mx.google.com>
MIME-Version: 1.0
To: "users@isis.apache.org" <users@isis.apache.org>
From: Nikhil Dhamapurkar <nikhil.dhamapurkar@healthengine.com.au>
Subject: Tenancy restriction - entity that relates to more than one Other
 entity.
Date: Thu, 30 Nov 2017 17:27:53 +0530
Importance: normal
Content-Type: multipart/alternative;
	boundary="_5DF1A687-CCA5-4735-AD6E-C09D4FCE8086_"
archived-at: Thu, 30 Nov 2017 11:58:00 -0000

--_5DF1A687-CCA5-4735-AD6E-C09D4FCE8086_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi,

I am working on supporting Multi Tenancy in Apache ISIS I have tried both  =
1) ApplicationTenancyEvaluator and 2) HasAtPath interfaces to control what =
the  logged in user can see or execute.

I have been able to make them work to an acceptable state but I face issue =
when I come across collections that are part of the entity I am evaluating.

My Domain model has Patient  / Practitioner entity both these entity can be=
 associated with Different Practices at the same time.


Example :    PractitionerA belongs to PracticeA and PracticeB both, logged =
in User has =E2=80=9CRole=E2=80=9D to Access PracticeA.

Issue with ApplicationTenancyEvaluator : since Practitioner and Practice ha=
ve many to many relation even if the role has access to only one practice I=
=E2=80=99ll end up displaying PracticeB on wicket viewer which I want to pr=
event, Is it possible ?


Issue with HasAtPath :=20

I am creating  Path programmatically with pattern as : ORG/org/PRACTICE/<pr=
acticeName>/  pattern which models a tree, then I can control user access t=
o more than one Patient data if user at path is /ORG/org Or restrict  acces=
s to one practice  /ORG/org/PRACTICE/practiceA=20
If the Patient Entity is associated with more than one practice My logic wi=
ll Break as I would not know what should be the context for the for ORG/org=
/PRACTICE/<WhatShouldBeHere?>

Does anyone have a better solution to tackle tenancy for a Collection withi=
n an entity?

Regards
Nikhil


--_5DF1A687-CCA5-4735-AD6E-C09D4FCE8086_--