Anonymous_User Absent Member.
Absent Member.
422 views

Define custom attribute with Static value in SAML Response


Hi,

We have a requirement to define a custom attribute with static value.
Static attribute was defined and the name of the static attribute is
coming in the SAML Response but the value is coming as *.* (like
below).

Appreciate any suggestions to resolve this issue.

;<saml:Attribute
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Name="SiteID"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic"><saml:AttributeValue
xsi:type="xsd:string">**</saml:AttributeValue>


Regards
Karthik


--
karthikeyan_palanisamy
------------------------------------------------------------------------
karthikeyan_palanisamy's Profile: http://forums.novell.com/member.php?userid=90439
View this thread: http://forums.novell.com/showthread.php?t=419665

Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Define custom attribute with Static value in SAML Response

karthikeyan palanisamy wrote:

>
> Hi,
>
> We have a requirement to define a custom attribute with static value.
> Static attribute was defined and the name of the static attribute is
> coming in the SAML Response but the value is coming as *.* (like
> below).
>
> Appreciate any suggestions to resolve this issue.
>
> ;<saml:Attribute
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> Name="SiteID"
> NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic&quo
> t;><saml:AttributeValue
> xsi:type="xsd:string">**</saml:AttributeValue>


If you captured the log file saml assertion all attribute values will
always display ** because of security. If you want to know what is
being sent in the assertion you could use capture the assertion in the
posted data (that is if you use HTTP/POST) and then b64 decode it.
You'll need a tool like fiddler to see posted data tho. Otherwise, a
packet trace should tell you but you'll have to decrypt traffic as
it'll be SSL-ed I'd say.


--
Cheers,
Edward
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.