APIM-4.1.0-Active-Active Setup - Step 9 - Optionally, enable distributed cache invalidation
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
This configuration has mentioned as "optional" in the documentation, but customers has reported some issues due not configuring this. As an example in an Active Active setup, if we regenerate the client secret of an application in one node, that change will not be reflected on the other node if this is not enabled. Therefore, access token requests on the other node fails.
And there is no explanation provided on why this is "optional" or what are the effects on the nodes.
Therefore, could you please check on this and improve the documentation ?
Best regards,
Amila.
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 at the linked Active-Active deployment documentation page and review Step 9, “Optionally, enable distributed cache invalidation.” Clarify why the setting is described as optional, explain its effects across nodes, and include the client-secret regeneration example. Done means readers can understand when the setting is needed and the consequences of leaving it disabled.
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
- Mostly clear
- Newbie friendliness
- 62/100