Documentation Issues Related to Refresh Token Grant
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
Issue 1:
In [1], under Generating a new access token and refresh token, in the response, access_token should be a JWT.
Issue 2:
In [2], under Revoking a refresh token -> Option 1 -> Response and Revoking a refresh token -> Option 2 -> Response POST and Host should be updated as follows. (Under Option 1 -> Response, POST is missing)
> POST /oauth2/revoke HTTP/1.1
> Host: localhost:9443
[1] https://apim.docs.wso2.com/en/4.1.0/design/api-security/oauth2/grant-types/refresh-token-grant/#generating-a-new-access-token-and-refresh-token
[2] https://apim.docs.wso2.com/en/4.1.0/design/api-security/oauth2/grant-types/refresh-token-grant/#revoking-a-refresh-token
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 two linked Refresh Token Grant documentation pages and review the “Generating a new access token and refresh token” and “Revoking a refresh token” sections. Update the access_token response to identify a JWT and correct both revocation response examples with the POST method and Host header shown in the issue, then verify both rendered examples.
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
- 50/100