[AMAGENTS-26] Attributes Processing does not map multiple values Created: 26/Feb/16  Updated: 01/Dec/16  Resolved: 07/Nov/16

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

Type: Bug Priority: Major
Reporter: Andrew Dunn [X] (Inactive) Assignee: Chris Lee
Resolution: Fixed Votes: 0
Labels: AMAgent, AME, SHAKESPEARE, regression-3-spec, 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: 11575, 15886
Support Ticket IDs:
Epic Link: Docs: Agents 4.1.0 Release

 Description   

If a profile attribute contains multiple values, only one of these is mapped to the header/cookie.

Steps to reproduce:
1. In Subjects -> demo, add two aliases to the list. "name1" and "name2".
2. Enable Profile Attributes Processing in header mode.
3. Add a mapping "iplanet-am-user-alias-list=alias"
4. Login as demo and access agent protected resources. Observe values in set header

Expected results:
Header of:

 [HTTP_ALIAS] => name1|name2

Actual result:

 [HTTP_ALIAS] => name1


 Comments   
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 22:23:05 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.