Point IS 7.3.0+ self-registration guide to the Flows guide (product-is#28312)

[sumuditha-V]

Purpose

Resolves wso2/product-is#28312

The legacy self-registration guide under Account configurations > User onboarding is no longer in the left navigation for IS 7.3.0, but it is still published and still reachable through search. It tells readers to go to Login & Registration > User Onboarding > Self Registration, a Console path that does not exist in 7.3.0 — self-registration moved to Flows > Self Registration (documented in guides/flows/self-registration).

This PR adds a version-gated note at the top of the shared include so readers who land on the legacy page from search are pointed to the current guide. The page itself is kept so that the content that is still accurate (customizing the registration attributes, retrieving account verification status via SCIM2) and the existing inbound links from other pages are not lost.

The note mirrors the pattern already used in this file for WSO2 Identity Platform, added in #6284.

Rendering, by is_version:

• 7.0.0 / 7.1.0 / 7.2.0 — unchanged, note not rendered.
• 7.3.0 and next — note rendered.
• Asgardeo / WSO2 Identity Platform — unchanged, gated on product_name.

Related PRs

• Add note for legacy password recovery and self registration docs to use the new flow based approaches #6284 — added the equivalent note for WSO2 Identity Platform on this same page.

Test environment

Documentation-only change; no product code involved. Verified the Jinja condition against the is_version value set in each mkdocs.yml under en/identity-server/ so that the note renders only for 7.3.0 and next and not for 7.0.0–7.2.0 or Asgardeo.

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report? — N/A, documentation-only change with no Java code.
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Caution

Review failed

Failed to post review comments.

GitHub was unavailable or timed out while CodeRabbit was posting the review. Please request a new review later if the pull request still needs one. This happened while posting 1 inline comment. Use @coderabbitai full review to retry the review.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 408214e0-45ac-41b6-b0df-5e0ddefbc8a8

📥 Commits

Reviewing files that changed from the base of the PR and between 4f7fcb7 and 539cd3e.

📒 Files selected for processing (1)

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.md: Use active voice and present tense; use passive voice only when the actor is unknown or unimportant
Use plain language and short sentences
Address the reader as 'you'
Keep a professional, friendly, neutral tone and avoid slang, jokes, sarcasm, and marketing language
Use official product and feature names exactly as defined; do not invent shorthand names, change capitalization, or alternate between long and short forms unless formally introduced
Define acronyms on first use unless universally known (API, URL, JSON, HTTP); after definition, use the acronym consistently and do not redefine within the same document
Use one term per concept; do not switch terminology mid-document or randomly mix expanded and abbreviated forms
Use standard technical terminology (e.g., server, endpoint, token, request, response, database, session) and avoid inventing alternative phrases for common concepts
Avoid ambiguous pronouns (it, this, that, they) by replacing them with explicit nouns when ambiguity exists
Reduce unnecessary use of weak 'be' verbs (am, is, are, was, were) and prefer direct verbs
Use precise nouns and strong verbs; avoid vague verbs such as handle, manage, deal with, perform, and utilize
In prose, use formal language: write 'configuration' instead of 'config', 'development' instead of 'dev', 'production' instead of 'prod', 'environment' instead of 'env', and 'repository' instead of 'repo' (shorthand allowed only in code blocks, file paths, commands, or environment variable names)
Use sentence case for all headings and document titles, capitalizing only the first word and proper nouns
Use numbered lists for procedures and ordered steps; use bulleted lists for non-sequential information; keep list items parallel in grammar and structure
Format UI labels, buttons, and menu items in bold
Format code elements, file names, paths, config keys, commands, and URLs in backticks
Use descriptive link text and do not paste raw URLs as link text
Use fenced code blocks wi...

Files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

🧠 Learnings (9)

📚 Learning: 2026-03-05T13:28:36.416Z

Learnt from: PasinduYeshan
Repo: wso2/docs-is PR: 5930
File: en/includes/guides/users/outbound-provisioning/provisioning-levels/org-level.md:10-10
Timestamp: 2026-03-05T13:28:36.416Z
Learning: In the wso2/docs-is repository, the version gating condition is_version > "7.2.0" uses string comparison in Jinja/MkDocs templates. This is the established convention and should not be flagged as a bug or suggested to replace with semantic version comparison. Apply this guideline to all markdown files processed by MkDocs/Jinja templates where the is_version variable is compared as a string; do not propose refactoring to semantic version parsing unless there is an explicit, repo-wide decision to change the convention.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-03-05T16:33:40.392Z

Learnt from: PasinduYeshan
Repo: wso2/docs-is PR: 5930
File: en/includes/guides/users/outbound-provisioning/provisioning-levels/application-level.md:46-46
Timestamp: 2026-03-05T16:33:40.392Z
Learning: In the wso2/docs-is repository, SCIM is treated as a known acronym in IAM documentation and should not be defined on first use. During reviews of markdown docs, do not flag SCIM as undefined. Apply this glossary convention consistently across all markdown files; if introducing other acronyms, ensure a glossary or definitions follow existing project guidelines.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-03-06T10:40:08.626Z

Learnt from: HasiniSama
Repo: wso2/docs-is PR: 5918
File: en/includes/guides/organization-management/api-authorization-for-b2b.md:28-28
Timestamp: 2026-03-06T10:40:08.626Z
Learning: Enforce the established terminology in the wso2/docs-is repository: use 'log in' as the verb and 'login' as the noun/adjective consistently across all Markdown documentation. Do not suggest replacing 'log in' with 'sign in' for user actions in any markdown files. If you see 'sign in' or inconsistent usage, convert to 'log in' (verb) or 'login' (noun/adjective) to maintain uniform documentation language.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-03-09T11:04:58.897Z

Learnt from: hwupathum
Repo: wso2/docs-is PR: 5950
File: en/includes/deploy/security/keystores/index.md:54-61
Timestamp: 2026-03-09T11:04:58.897Z
Learning: In the wso2/docs-is repository, treat SAML, OIDC, and OAuth as known acronyms in IAM documentation and do not expand them on first use. Apply this convention consistently across all Markdown files in the repository (any .md). When encountering these acronyms, use the abbreviations (SAML, OIDC, OAuth) without introducing their full forms on first use.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-04-19T16:23:42.995Z

Learnt from: ranuka-laksika
Repo: wso2/docs-is PR: 6039
File: en/asgardeo/docs/tutorials/end-to-end-mcp-authorization-with-asgardeo.md:116-117
Timestamp: 2026-04-19T16:23:42.995Z
Learning: In the wso2/docs-is repository’s Markdown files, treat MD007 as an exception for nested list items: sub-lists that are intended to render correctly in MkDocs (Python-Markdown) may use 4-space indentation. Do not report MD007 violations for nested list item indentation that follows the 4-space sub-list convention, even though MD007’s CommonMark expectation is 2 spaces.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-04-21T16:09:56.532Z

Learnt from: SujanSanjula96
Repo: wso2/docs-is PR: 6068
File: en/includes/guides/organization-management/organization-discovery/organization-discovery-enhanced-flow.md:71-75
Timestamp: 2026-04-21T16:09:56.532Z
Learning: In wso2/docs-is markdown files, treat the Base64 string `YWRtaW46YWRtaW4=` (decodes to `admin:admin`) as an intentional, docs-wide placeholder commonly used in `curl` Authorization: Basic header examples. Do not raise findings for “hardcoded credentials” or “security issue” for this specific value in documentation; it is meant only to illustrate API request formatting and is not intended for production use.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-03-10T10:09:56.036Z

Learnt from: PasinduYeshan
Repo: wso2/docs-is PR: 5930
File: en/includes/guides/users/outbound-provisioning/group-based-provisioning.md:23-23
Timestamp: 2026-03-10T10:09:56.036Z
Learning: Do not flag image references as missing in include files under en/includes/ when those includes are exclusively consumed by version-specific documentation directories (e.g., Asgardeo or IS next/versions > 7.2.0) where the referenced image assets are known to exist. Apply this only if the include is referenced solely from those versioned paths; otherwise perform standard image-access checks.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-04-03T08:17:54.213Z

Learnt from: HasiniSama
Repo: wso2/docs-is PR: 6034
File: en/includes/guides/organization-management/disable-delete-organizations.md:37-39
Timestamp: 2026-04-03T08:17:54.213Z
Learning: In wso2/docs-is markdown files under en/includes/ (and specifically within MkDocs admonitions like `!!! note`), if you have a Jinja/Liquid `{% if %}...{% endif %}` conditional block, ensure Markdown list items both inside and outside the conditional are indented by 8 spaces (not the usual 4) so they stay correctly scoped within the admonition. This is an intentional indentation requirement for correct rendering; do not flag it as an indentation issue in these markdown files when it is used to preserve admonition scoping around Jinja conditionals.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📚 Learning: 2026-04-02T11:13:01.673Z

Learnt from: ShanChathusanda93
Repo: wso2/docs-is PR: 6031
File: en/includes/guides/organization-management/generate-tokens-for-organization-apps.md:162-162
Timestamp: 2026-04-02T11:13:01.673Z
Learning: In wso2/docs-is documentation markdown files under en/includes/guides/, “Sample request” tabs may intentionally include fictional but realistic-looking OAuth credential strings (e.g., strings formatted like `<OAUTH_CLIENT_KEY>:<OAUTH_CLIENT_SECRET>` such as `fhErtAT2YF_...:Jirxv...`). These are NOT real credentials and should not be flagged as security issues. Only “Request format” tabs should use proper placeholders like `<OAUTH_CLIENT_KEY>:<OAUTH_CLIENT_SECRET>`.

Applied to files:

• en/includes/guides/account-configurations/user-onboarding/self-registration.md

📝 Walkthrough

Walkthrough

The self-registration guide now warns that its Console instructions apply to Identity Server 7.2.0 and earlier. It directs users of version 7.3.0 and later to Flows > Self Registration.

Changes

Self-registration documentation

Layer / File(s)	Summary
Version-specific self-registration guidance en/includes/guides/account-configurations/user-onboarding/self-registration.md	Adds a warning for Identity Server 7.3.0 and later. The warning directs readers to configure self-registration under Flows > Self Registration.

Suggested labels: Team/Authentication & registration

Suggested reviewers: himeshsiriwardana

Merge Risk: ⚪ Minimal · up to 539cd

The PR updates the legacy self-registration guidance for IS 7.3.0 without affecting product code or runtime behavior. No actionable merge-blocking risk remains; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the IS 7.3.0+ self-registration guide update and its direction to the Flows guide.
Description check	✅ Passed	The description covers the purpose, issue, related PR, test scope, rendering behavior, and security checks.
Linked Issues check	✅ Passed	The change addresses issue #28312 by directing IS 7.3.0+ users from the obsolete path to Flows > Self Registration while preserving valid content.
Out of Scope Changes check	✅ Passed	The pull request contains only the documented version-gated note required for issue #28312.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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.}