Correction Required in Sample Custom JWT Generator
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Current Limitation
Hi Team,
The sample Custom JWT Generator provided in the official documentation[1] contains an issue where the WSO2 internal repository is referenced using an HTTP[2] URL. This causes the build process to fail and should be corrected to use HTTPS instead. Similar issues may be there in other samples across the documentation and should also be reviewed and corrected accordingly.
[1] https://apim.docs.wso2.com/en/latest/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/passing-enduser-attributes-to-the-backend-via-api-gateway/#:~:text=Click%20here%20for%20a%20sample%20Custom%20JWT%20Generator.
[2] https://github.com/wso2/samples-apim/blob/f2fc32a6f46c3b43f8e6b96469de019b56691057/CustomJWTGenerator/pom.xml#L43
Thanks,
Sameera
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 API Gateway documentation section and the referenced samples-apim CustomJWTGenerator/pom.xml at line 43. Verify the repository URL uses HTTPS, review nearby documentation samples for similar HTTP repository references, and confirm the corrected links allow the sample build to proceed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100