[AMAGENTS-2528] Documentation required for new policy cache feature Created: 22/Feb/19  Updated: 27/Mar/19  Resolved: 13/Mar/19

Status: Resolved
Project: OpenAM Agents
Component/s: Doc, Web Agents
Fix Version/s:

Type: Task
Reporter: edwardb Assignee: Chris Lee
Resolution: Fixed Votes: 0
Labels: 5.6-Must-Fix, AME, SHAKESPEARE, documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by AMAGENTS-2117 Document the local policy index featu... Resolved
Target Version/s:
Story Points: 3
Sprint: 2019.4
Epic Link: Docs: Agents


For the release, the new policy cache feature will be available as a non-supported technology preview.

There is a section at the end of https://docs.google.com/document/d/1mEUZQ1nYm0wkcOQCbUBa8t4y7LdpE9CszGPyk2n5xZg/edit which contains details about what we think would need to go into the docs.

Comment by Chris Lee [ 06/Mar/19 ]

Hi edwardb and Nicholas James - what are the differences between this new feature, and the existing WPA policy cache, as described here: https://backstage.forgerock.com/docs/openam-web-policy-agents/5.5/web-agents-guide/#web-agent-caching-capabilities

How will these two work alongside each other? Is the new feature a replacement of the documented one? Can/should they be used in unison?

Any and all info appreciated.

Comment by edwardb [ 06/Mar/19 ]

The appendix in https://docs.google.com/document/d/1mEUZQ1nYm0wkcOQCbUBa8t4y7LdpE9CszGPyk2n5xZg/edit has details about how this cache is different to the existing WPA policy cache.

The feature is either switched off or on. If it is on then the way the policy cache works will change so that it behaves as described in https://docs.google.com/document/d/1mEUZQ1nYm0wkcOQCbUBa8t4y7LdpE9CszGPyk2n5xZg/edit.

From what I understand. https://backstage.forgerock.com/docs/openam-web-policy-agents/5.5/web-agents-guide/#web-agent-caching-capabilities - The session cache should not be affected and the described features such as com.sun.identity.agents.config.policy.cache.polling.interval should still work as described. Is this correct Nicholas James

Comment by Nicholas James [ 06/Mar/19 ]

Yes its correct.

Generated at Sat Feb 27 03:20:33 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.