[Doc Issue] Scope Management Endpoint marked optional for Keycloak Key Manager
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description
Configure Keycloak as a Key Manager
The documentation for configuring Keycloak as a Key Manager in WSO2 API Manager 4.7.0 says that the Scope Management Endpoint is optional. However, in the APIM Admin Portal, the field is mandatory and the Key Manager cannot be added without it.
This creates a mismatch between the documentation and the actual product behavior.
Steps to Reproduce
- Open WSO2 APIM 4.7.0 Admin Portal.
- Go to Key Managers.
- Add a new Keycloak Key Manager.
- Fill the configuration fields.
- Leave Scope Management Endpoint empty, based on the documentation.
- Try to save the Key Manager.
Version
API-M-4.7.0
Environment Details (with versions)
OS: Ubuntu 24.04
Key Manager: Keycloak 25.0.6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked Configure Keycloak as a Key Manager page and review the Scope Management Endpoint guidance for API-M 4.7.0. Compare it with the Admin Portal behavior described in the issue, then update the documentation so the requirement is accurate and verify the rendered page.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100