[APIM 4.x.x ] Recommendation to Enable Deep Cleaning in Multiple Active Access Tokens Documentation
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,
When the Multiple Active Access Tokens configuration[1] is enabled in APIM, the 'IDN_OAUTH2_ACCESS_TOKEN' table may grow rapidly over time, which could lead to multiple issues. Therefore, this documentation[1] should include a note emphasizing the importance of enabling deep cleaning[2], especially when using this configuration[1].
[1] https://apim.docs.wso2.com/en/4.2.0/design/api-security/oauth2/multiple-active-access-tokens/
[2] https://apim.docs.wso2.com/en/4.2.0/install-and-setup/setup/setting-up-databases/managing-data-growth-and-improving-performance/#deep-cleaning
Thanks,
Sameera
Version
4.0.0
4.1.0
4.2.0
4.3.0
4.4.0
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 Multiple Active Access Tokens documentation linked as [1], then read the Deep Cleaning section linked as [2]. Add a note explaining that deep cleaning is important when Multiple Active Access Tokens is enabled, and verify that the guidance applies across the listed APIM 4.x versions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100