[AMAGENTS-42] Percent encoded hash (#) (%23) is handled incorrectly during policy evaluation Created: 11/Mar/16  Updated: 13/Apr/17  Resolved: 01/Dec/16

Status: Closed
Project: OpenAM Agents
Component/s: Doc, Web Agents
Affects Version/s: 3.3.4, 4.0.0
Fix Version/s:, 4.1.0

Type: Bug Priority: Major
Reporter: Ian Packer [X] (Inactive) Assignee: Chris Lee
Resolution: Fixed Votes: 0
Labels: AMAgent, AME, SHAKESPEARE, incomplete-spec, interface, release-notes, test-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Verified Version/s:
QA Assignee: edwardb
Sprint: Sprint 115 Team Shakespeare
Cases: 11522
Support Ticket IDs:
Epic Link: Docs: Agents 4.1.0 Release


Steps to reproduce

1) Setup OpenAM with Web Agent (3.3.x or 4.0.x)
2) Add a simple all users policy to allow access to everything, e.g "http://www.example.com/*"
3) Attempt to access http://www.example.com/test%23test


Access is denied

Expected result:

Access is allowed

Adding a rule for www.example.com/test#test or # works, but this is not a good workaround because the file could include many encoded # characters and each variation of this would require it's own rule.

I think the two key points are:

In OpenAM the wildcard character stops at a literal # character (much like ?).
The Agent decodes the %23 before sending it for evaluation to OpenAM.

Comment by Peter Major [X] (Inactive) [ 11/Mar/16 ]

Sounds like the agent shouldn't decode the %23 character when performing the policy evaluation. The server side code will always parse the URL, and then a literal # will be taken as the fragment, hence rule matching may not work as expected.

Comment by edwardb [ 14/Oct/16 ]

Verified with OpenAM13.0.0 and Agent 4.1.0

Comment by Chris Lee [ 07/Nov/16 ]

To appear in the release notes queries the Jira must:

  1. Have the Resolved status.
  2. Have the fixVersion set to the versions of the release to appear in.
  3. Have the `release-notes` label.

Where there is some manual documentation work to perform, for example a breaking change from a previous version, please create us a separate documentation Jira.
Marking as resolved so it appears in the release notes.

Generated at Mon Mar 01 21:45:20 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.