Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for application tenancy paths without requiring an actual application tenancy #16

Closed
danhaywood opened this issue Mar 27, 2015 · 1 comment
Closed

Add support for application tenancy paths without requiring an actual application tenancy #16

danhaywood opened this issue Mar 27, 2015 · 1 comment

Comments

@danhaywood
Copy link
Contributor

... the idea being that if an implementation of a new "ApplicationTenancyPathEvaluator" domain service is available, then it should be used to obtain the paths of the object and the appuser in order for the TenantedAuthorizationFacetDefault to determine whether to veto access.
danhaywood added a commit that referenced this issue Mar 27, 2015
@danhaywood
#16 - introducing ApplicatoinTenancyPathEvaluator interface
f45e9c9
@danhaywood
Copy link
Contributor Author

Implemented in f45e9c9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danhaywood