Improve Auth0 as KM Documentation
Open
Nobody has claimed this yet.
DevRel
Type/Improvement
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Current Limitation
The document has some unclear points and need them to be fixed.
Doc Link - https://apim.docs.wso2.com/en/latest/administer/key-managers/configure-auth0-connector/
Suggested Improvement
- Modify the auth0 link in https://apim.docs.wso2.com/en/latest/manage-apis/deploy-and-publish/deploy-on-gateway/federated-gateways/deploy-on-aws-api-gateway/#step-3-configure-a-third-party-key-manager
- Modify the steps to click import after adding the wellknown address in https://apim.docs.wso2.com/en/latest/administer/key-managers/configure-auth0-connector/#step-2-configure-wso2-api-manager
- The scope management endpoint is marked as mandatory in the UI although it is given as optional in the doc - Check and modify the doc accordingly - https://apim.docs.wso2.com/en/latest/administer/key-managers/configure-auth0-connector/#step-2-configure-wso2-api-manager
- Provide the same authorize endpoint as the scope endpoint and proceed
- The document seems bit messy with the large images, format it and make the instructions more clear. Specially it is not clear to put the audience value when generating keys for the application.
Version
No response
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
Start with the Auth0 connector document at /administer/key-managers/configure-auth0-connector/ and compare its instructions with the linked federated gateway page. Review the import step, endpoint and audience guidance, optional scope-management wording, links, and image layout. Done means the referenced instructions are consistent, clear, and formatted for readers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100