Repository navigation
Conversation
Resolve the caller's reach the way rest-api does and keep the tenants list, lookups and creates inside it. PLACE_TENANCY_ENFORCE switches between refusing and logging. Builds against the models tenancy branch until models #332 merges.
18 of 20 tasks
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tenant administration is limited to the caller's structural reach and the live grant permissions required for each operation. Management partner users gain cluster reach only from a staff organisation; authority grants cover exactly one domain, read grants cannot authorise writes, and tenant updates validate the destination domain. Existing JWT scope and admin checks still apply.
Spaces use the domain's configured
org_zone. When it is absent, the fallback reads only organisation-owned rooms/zones after verifying that the organisation has one domain and its owned rooms reference owned zones. Ambiguous configuration returns HTTP 501 with anorg_zonemessage. Asset-type creation and updates validate the destination category authority, preserving legacy NULL-authority category support.Staff API retains its authenticated Host/JWT, email-domain Tenant, parent Tenant and calendar/delegated-credential context. This PR also fixes an existing calendar spec's dependence on cached OAuth tokens. README configuration guidance and generated OpenAPI schemas are updated.
Requires the ownership foundation in PlaceOS/models#332; the models tenancy dependency is pinned at
716ca76until that foundation is released. Related rollout seeding: PlaceOS/init#105. Tracking: #396 and PlaceOS/rest-api#465.Review
a9b8a21; the PR remains a draft.