[AMAGENTS-262] Update cookie reset properties to reflect new behaviour of AMAGENTS-247 Created: 10/Nov/16  Updated: 14/Aug/18  Resolved: 18/Jan/18

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

Type: Improvement Priority: Major
Reporter: Joe Starling Assignee: Cristina Herraz
Resolution: Fixed Votes: 0
Labels: AME, SHAKESPEARE, documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Epic Link: Docs: Agents

 Description   

The cookie reset properties should be updated to reflect the changes introduced in AMAGENTS-247

https://backstage.forgerock.com/docs/openam-web-policy-agents/4/web-users-guide/chap-web-agents#web-agent-cookie-reset-properties

The following is now possible. Previously, Path would always default to "Path=/":

CookieName=foo;Domain=.forgerock.com;Path=/bar

Strangely, this section already mentions that you can specify the Path, even though it wasn’t possible previously

https://backstage.forgerock.com/docs/openam-web-policy-agents/4/web-users-guide/chap-agent-features#cookie-reset

Additionally:

There is a link in the OpenAM admin guide taking you to the Agents configuration doc (see here https://backstage.forgerock.com/docs/openam/13.5/admin-guide/chap-agents#configure-web-policy-agent).

The link is wrong (404):

https://backstage.forgerock.com/docs/openam-web-policy-agents/web-users-guide/configure-web-policy-agent

I believe the correct url would be this, or its equivalent?

https://backstage.forgerock.com/docs/openam-web-policy-agents/4/web-users-guide#chap-web-agents



 Comments   
Comment by Cristina Herraz [ 14/Dec/17 ]

Had a chat with Nick about this.

This property should be set up like this

com.sun.identity.agents.config.cookie.reset[0]="myCookie"

From agents 4. Java agents are the ones that could specify domain and such. It seems that is what the change is in 4.1.1, which never made it to agents 5. So, I'll decline my PR and will open a new one to correct agents 5 docs. When documenting this Jira for 4.1.1, check the old PR since it has all the info needed for the changes.

Comment by Cristina Herraz [ 18/Jan/18 ]

Fixed in 4.1.1, and reworked in agents 5

Generated at Mon Mar 01 22:36:59 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.