Add link to Asgardeo–InCountry integration guide

[pamodaaw]

Purpose

Asgardeo supports integrating with InCountry, a data residency / data localization platform, but the docs had no link to the integration guide. This PR surfaces that link in a discoverable, topically relevant place.

Changes

Adds an "Extended data residency with InCountry" section to the Asgardeo data residency reference page (en/asgardeo/docs/references/data-residency-in-asgardeo.md), just before the "Get support" section. It links to the partner-hosted guide: https://incountry.com/integrations/wso2-asgardeo/

InCountry lets organizations keep identity data within a specific country's borders (beyond the built-in US/EU regional data centers), so the data residency page is where readers with those requirements will look.

Conventions followed

• Uses {{product_name}} templating (page is shared between Asgardeo and WSO2 Identity Server).
• Uses {:target="_blank"} on external links, matching the existing Moesif link on the page.
• No mkdocs.yml nav change needed — the page is already in the nav under References.

🤖 Generated with Claude Code

[coderabbitai]

📝 Walkthrough

Walkthrough

Changes

Data residency documentation

Layer / File(s)	Summary
InCountry residency guidance en/asgardeo/docs/references/data-residency-in-asgardeo.md	Adds a subsection describing InCountry-based country-level identity data residency and linking to the setup guide.

Possibly related PRs

• wso2/docs-is#6264: Updates the same data-residency documentation file with India-related data-sharing information.

Suggested labels: Team/Identity Server Core

Suggested reviewers: bhagyasakalanka, lakshan-banneheke, savindi7

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers Purpose, but it omits required template sections like Related PRs, Test environment, and Security checks.	Add the missing template sections: Related PRs, Test environment, and Security checks, or mark them explicitly as not applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main change: adding the Asgardeo–InCountry integration guide link.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/asgardeo/docs/references/data-residency-in-asgardeo.md`:
- Line 124: Update the link in the surrounding documentation to match the
destination: either replace the target with the actual InCountry setup
instructions, or rename the existing link text to “integration overview” instead
of describing it as a setup guide.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 065d8645-2901-4ea1-a8b7-f9f7f8729820

📥 Commits

Reviewing files that changed from the base of the PR and between 321e4a1 and d7020f6.

📒 Files selected for processing (1)

• en/asgardeo/docs/references/data-residency-in-asgardeo.md

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

InCountry WSO2 Asgardeo integration guide setup instructions overview

💡 Result:

InCountry integration with WSO2 Asgardeo is a specialized solution designed to provide enhanced data residency and sovereignty by isolating sensitive identity data within specific countries, rather than relying solely on the regional data centers provided natively by Asgardeo [1][2][3]. Integration Overview WSO2 Asgardeo has been integrated with InCountry services to allow organizations to meet complex regulatory requirements by retaining personal user data within a chosen territory [2]. This integration functions as an optional service that supplements the standard Asgardeo subscription [2]. Key Capabilities - Data Cloaking and Isolation: The integration uses secure digital twins to isolate identity profiles within a country [1]. It cloaks and uncloaks identity fields (in forms, registration, login) and JWT authorization token claims [1]. - No Code Changes Required: The solution leverages SCIM 2.0 and vendor API cloaking, allowing it to function without necessitating significant code changes in your existing application architecture [1]. - Sovereign AI and Data Protection: It supports AI data protection, enabling the cloaking of payloads for AI agents to comply with data minimization requirements, such as those found in the EU AI Act [1]. How it Works Integration typically involves InCountry's middleware or proxy services to process data transparently [1][4]. - Transparent Redaction (InCountry Border): A common deployment method involves using the InCountry Border proxy server [4]. By configuring your application to communicate through this proxy, sensitive data is automatically processed, cloaked, or redirected to local storage before it reaches or returns from your main servers [1][4]. - On-Demand Redaction: For more complex or granular needs, applications can explicitly call the InCountry API to manage the redaction and tokenization of specific data fields manually [4]. Implementation Steps (Conceptual) 1. Subscription: Because this is a partner solution, organizations must execute relevant order forms with WSO2 and, if applicable, agree to InCountry’s terms of service and support policies [2]. 2. Configuration: Deployment and configuration are managed via the InCountry portal, where you define the target server URLs and data masking rules [1][4]. 3. Proxy Setup: If using transparent redaction, you update your application configuration to point to the InCountry proxy URL instead of the direct Asgardeo or backend API endpoints [1][4]. Note: For deployments specifically within China, the service is facilitated through DCC (Data Center China), requiring a separate agreement with that entity to enable the integration [2]. Organizations should consult their WSO2 account representative to initiate the provisioning of InCountry services [2].

Citations:

• 1: https://incountry.com/integrations/wso2-asgardeo/
• 2: https://wso2.com/licenses/third-party-software-and-solutions
• 3: https://wso2.com/library/conference/2026/05/how-to-add-multi-country-data-residency-and-data-sovereignty-for-wso2-identity-wso2-ai-and-api-gateways
• 4: https://docs.incountry.com/data-residency-as-a-service/tutorial/

---

Update the link text or target The InCountry page is an integration overview, not a setup guide. Link to the setup instructions or rename this link to “integration overview.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@en/asgardeo/docs/references/data-residency-in-asgardeo.md` at line 124,
Update the link in the surrounding documentation to match the destination:
either replace the target with the actual InCountry setup instructions, or
rename the existing link text to “integration overview” instead of describing it
as a setup guide.

Source: MCP tools