You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2022/04/15 22:01:00 UTC

[jira] [Commented] (DIRSTUDIO-1296) Export doesn't decode RFC 4517 Postal Address syntax

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522952#comment-17522952 ] 

Emmanuel Lécharny commented on DIRSTUDIO-1296:
----------------------------------------------

Hi Frederik,

It's not exactly a bug, it's more a choice that has been made to show and manipulate the data as they are expected to be stored in the LDAP server.
Now, the question is: does it makes sense? The PostalAddress syntax, as described and defined in RFC 4517, is for internal usage, in order to guarantee that values can be safely compared and searched. In some way, what happens *outside* of the LDAP server is irrelevant, and we could simply decode the internal representation (the one provided in RFC 4517), removing the spurious escapes and '$' to render something that is human readable. The only condition is that we can do the reverse work before injecting the data in a LDAP server - ie we escape $, \ end replace newlines by '$' -.

Assuming the last part is done in Studio, your proposal makes much sense to me.

Stefan, your take ?


> Export doesn't decode RFC 4517 Postal Address syntax
> ----------------------------------------------------
>
>                 Key: DIRSTUDIO-1296
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1296
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M17
>            Reporter: Fredrik Roubert
>            Priority: Major
>
> When exporting any entries using the RFC 4517 Postal Address syntax (1.3.6.1.4.1.1466.115.121.1.41) to any non-LDAP data format (CSV, Excel, …) these entries aren't decoded but the RFC 4517 escaped data is instead exported as-is, like this:
> \241,000,000 Sweepstakes$PO Box 1000000$Anytown, CA 12345$USA
> … instead of this:
> $1,000,000 Sweepstakes
> {{PO Box 1000000}}
> {{Anytown, CA 12345}}
> {{USA}}
> I think it's safe to assume that no non-LDAP software is expected to be able to decode RFC 4517 escaped data, so not doing this decoding upon export must be a bug.
> (This data is correctly decoded and encoded by default for display and edit within Directory Studio itself.)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org