Skip to content

feat: report caller org ASO tier on cross-org sites-resolve - #2980

Open
sandsinh wants to merge 2 commits into
mainfrom
SITES-48838-cross-org-aso-tier
Open

feat: report caller org ASO tier on cross-org sites-resolve#2980
sandsinh wants to merge 2 commits into
mainfrom
SITES-48838-cross-org-aso-tier

Conversation

@sandsinh

Copy link
Copy Markdown
Contributor

When callerImsOrg is present on GET /sites/resolve and differs from the target org's imsOrgId (a cross-org caller — e.g. an AEC shell in org A viewing org B), the asoTier field now reports the caller org's ASO tier instead of the target org's, so the UI gates on the shell's own tier.

  • Applies to every asoTier emission (success and failure) for the resolved target org.
  • isSummitPlgEnabled stays target-derived — only asoTier is overridden.
  • Falls back to the target org's tier when the caller org is not in the DB (its tier is unknowable); no override when callerImsOrg matches the target.
  • Org-not-found / access-denied paths keep asoTier: null unchanged.

Adds unit tests and updates the OpenAPI callerImsOrg/asoTier docs.

Please ensure your pull request adheres to the following guidelines:

  • make sure to link the related issues in this description. Or if there's no issue created, make sure you
    describe here the problem you're solving.
  • when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

  • make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
    yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
  • make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

  • make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

  • make sure you update the API specification with the type, schema of the audit result and an example

Related Issues

https://jira.corp.adobe.com/browse/SITES-48838

Thanks for contributing!

…8838

When callerImsOrg is present on GET /sites/resolve and differs from the
target org's imsOrgId (a cross-org caller — e.g. an AEC shell in org A
viewing org B), the asoTier field now reports the caller org's ASO tier
instead of the target org's, so the UI gates on the shell's own tier.

- Applies to every asoTier emission (success and failure) for the resolved
  target org.
- isSummitPlgEnabled stays target-derived — only asoTier is overridden.
- Falls back to the target org's tier when the caller org is not in the DB
  (its tier is unknowable); no override when callerImsOrg matches the target.
- Org-not-found / access-denied paths keep asoTier: null unchanged.

Adds unit tests and updates the OpenAPI callerImsOrg/asoTier docs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@codecov

codecov Bot commented Jul 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions

Copy link
Copy Markdown

This PR will trigger a minor release when merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant