Highlighted
Anonymous_User Absent Member.
Absent Member.
291 views

Encoding givenName attribute


Hi all,

I have integrated a new SP in my environment.
In the SAML response, we transfer different attributes including the
user first name.
Everything works fine... except for me! 😞

After investigating, I found that the SP does not like the SAML response
because I have a "ë" (a special character) in my name. (error message is
" Input is not proper UTF-8, indicate encoding !").
If I replace the "ë" with a "e", it works fine.

So I would like to know if it is possible to encode an LDAP attribute
before sending it into the SAML response.
Or how can I solve this issue?

Thank you for your help!


--
marieno2
------------------------------------------------------------------------
marieno2's Profile: https://forums.netiq.com/member.php?userid=417
View this thread: https://forums.netiq.com/showthread.php?t=47857

0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Encoding givenName attribute


marieno2;229928 Wrote:
> Hi all,
>
> I have integrated a new SP in my environment.
> In the SAML response, we transfer different attributes including the
> user first name.
> Everything works fine... except for me! 😞
>
> After investigating, I found that the SP does not like the SAML response
> because I have a "ë" (a special character) in my name. (error message is
> " Input is not proper UTF-8, indicate encoding !").
> If I replace the "ë" with a "e", it works fine.
>
> So I would like to know if it is possible to encode an LDAP attribute
> before sending it into the SAML response.
> Or how can I solve this issue?
>
> Thank you for your help!


It's been quite some time since this post was made, but still I hope
someone can help me (and the OP) with this issue.

I have the same issue in my environment where I have setup a SAML 2.0
trust with a Service Provider. When I login to AM using an account that
has diacritics characters (é, ë, etc.) the SP cannot process the SAML
token, due to the encoding. The SP says the message is encoded as
Latin-1 and by default the SP expects UTF-8 unless told otherwise.

Is there a way to either:
a) Set the encoding to UTF-8
b) Make sure the SAML token contains a tag that says it's Latin-1
encoded.

Any help here would be very much appreciated.


--
esauve
------------------------------------------------------------------------
esauve's Profile: https://forums.netiq.com/member.php?userid=281
View this thread: https://forums.netiq.com/showthread.php?t=47857

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.