On Mar 25, 2014 8:31 AM, "Emmanuel Lécharny" <[email protected]> wrote:
>
> Le 3/25/14 1:09 PM, Lucas Theisen a écrit :
> > On Mar 25, 2014 2:48 AM, "Kiran Ayyagari" <[email protected]> wrote:
> >>
> >>
> >>
> >> On Tue, Mar 25, 2014 at 5:08 AM, Emmanuel Lécharny <[email protected]
>
> > wrote:
> >>> Hi guys,
> >>>
> >>> now hat I cleaned up the extended operation code, I'm implementing the
> >>> WhoAmI operation (RFC 4532).
> >>>
> >>> The response is supposed to send back the authId, which is either an
> >>> userId or a Dn id (depends on if it staets with 'u:' or 'dn:').
> >>>
> >>> At this point, the RFC stipulates that the content is eiher a valid DN
> >>> ('dn:...') or a set of UTF8 ('u:...'), which means we should keep the
> >>> content as a byte[]. Now, all the exemples I see o the web are
> >>> considering the value as a String, so what about exposing this
interface
> > :
> >>> WhoAmIResponse {
> >>> boolean isDn()
> >>> boolean isUserId
> >>> byte[] getAuthzId()
> >> would be nice to have a "String getAuthzIdUtf8()" method as well
> > I would probably suggest a more standard "String getAuthzId( Charset )"
if
> > the overload is necessary...
>
> I have even something simpler :
>
> String getAuthzIdString();
>
> There is no reason to pass a Charset, as the data will be UTF-8 encoded,
> and we willr return a String.
Agreed.
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
