Bug 1131313 - NameFormat should be mutable
Summary: NameFormat should be mutable
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: EAP 6.4.0
Assignee: Pedro Igor
QA Contact: Josef Cacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-19 02:34 UTC by Hisanobu Okuda
Modified: 2019-10-10 09:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 21:16:48 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLINK-550 0 Major Resolved NameFormat should be mutable 2016-07-05 12:57:02 UTC
Red Hat Issue Tracker PRODMGT-976 0 Major Open NameFormat should be mutable 2016-07-05 12:57:02 UTC

Description Hisanobu Okuda 2014-08-19 02:34:40 UTC 
Description of problem:
You can add AttributeStatement to SAML assertion implementing org.picketlink.identity.federation.core.interfaces.AttributeManager.

However, the value of NameFormat in AttributeStatement is hard-coded to "urn:oasis:names:tc:SAML:2.0:attrname-format:uri" in org.picketlink.identity.federation.core.saml.v2.util.StatementUtil.createAttributeStatement(Map<String, Object> attributes). It should be mutable, eg, "urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 JBoss JIRA Server 2014-10-04 06:21:44 UTC 
Pedro Igor <pigor.craveiro> updated the status of jira PLINK-550 to Resolved
Comment 28 Brad Maxwell 2016-03-09 21:16:48 UTC 
This is feature request, feature request go in PRODMGT, this issue is tracked by PRODMGT-976.  Closing as per this is a feature request and there are no more feature releases for EAP 6.x
Note You need to log in before you can comment on or make changes to this bug.