Skip to content

Update WSO2 IS connector configuration instructions#11288

Open
yuwani-004 wants to merge 1 commit intowso2:masterfrom
yuwani-004:master
Open

Update WSO2 IS connector configuration instructions#11288
yuwani-004 wants to merge 1 commit intowso2:masterfrom
yuwani-004:master

Conversation

@yuwani-004
Copy link
Copy Markdown

Added configuration instructions for OAuth applications ownership and scopes.

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

  • Unit tests

    Code coverage information

  • Integration tests

    Details about the test cases and coverage

Security checks

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Added configuration instructions for OAuth applications ownership and scopes.
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented May 5, 2026

CLA assistant check
All committers have signed the CLA.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 01a8e90a-8205-4f22-8d37-82147fa60292

📥 Commits

Reviewing files that changed from the base of the PR and between ab1aeac and 8e65cdc.

📒 Files selected for processing (1)
  • en/docs/api-security/key-management/third-party-key-managers/configure-wso2is-connector.md

📝 Walkthrough

Summary

This pull request adds configuration guidance to the WSO2 IS connector documentation. Specifically, a new note has been added to Step 1 of the configuration instructions that addresses scenarios where application owner users are not created on the WSO2 IS side.

The note provides the additional deployment.toml configuration settings required to:

  • Enable OAuth applications to be owned by the admin user
  • Enable application scopes through the oauth.scope_validator section

The change consists of 10 new lines of documentation including code examples showing the required configuration parameters.

Walkthrough

A note has been added to Step 1 of the WSO2 IS connector configuration documentation. The note instructs that when application owner users are not created on the WSO2 IS side, specific deployment.toml configuration settings must be applied to enable admin user ownership of OAuth applications and to activate application scopes through the oauth.scope_validator section.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description is largely incomplete. Only the summary line is filled in; all required template sections (Purpose, Goals, Approach, User stories, Release note, etc.) contain only placeholder text without substantive content. Complete the required sections of the PR description template with specific details about the purpose, goals, approach, and other applicable sections relevant to this documentation change.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: updating WSO2 IS connector configuration instructions. It is directly related to the documentation update in the changeset.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

Comment @coderabbitai help to get the list of available commands and usage tips.

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.

2 participants