wso2 / wso2/docs-apim

Improvements to Configure the Azure AD as a Key Manager doc

Open Beginner friendly
#10,460 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type/Improvement
Dominant language
CSS
Stars
99
Forks
708
Avg merge
1d 7h
Merged PRs (30d)
22

Description

Description

In Configure the Azure AD as a Key Manager, the following places can be improved.

Suggested Improvement

  1. For the Scope Management Endpoint field it says The endpoint is used to manage the scopes. It would be better if we could mention how to obtain this endpoint. In my case, I have used https://<host>:9443/oauth2/scope and it worked. We can provide this value in the doc if it is always the case.

  2. In Troubleshooting Invalid Credentials Error, it talks about the iss of the token. It would be better if we mentioned how we can obtain iss from a token. Simply saying decode token to get iss is enough.

Version(s)

4.6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Configure the Azure AD as a Key Manager page and locate the Scope Management Endpoint field and the Troubleshooting Invalid Credentials Error section. Clarify how to obtain the endpoint, including whether https://:9443/oauth2/scope is generally applicable, and explain that decoding the token reveals its iss value.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.