[
https://issues.apache.org/jira/browse/ISIS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778824#comment-13778824
]
ASF subversion and git services commented on ISIS-546:
------------------------------------------------------
Commit 98fa9f2d9204166c1b9168d1f0839dd161d0e61e in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=98fa9f2 ]
ISIS-546: oid marshalled can contain '@' in username
> OID marshalling should allow an '@' symbol for the version.getUser()
> --------------------------------------------------------------------
>
> Key: ISIS-546
> URL: https://issues.apache.org/jira/browse/ISIS-546
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: core-1.3.0
>
>
> In testing Estatio's LDAP integration, have found that the userId contains an
> '@' symbol. When this is marshalled into an OID (as part of the
> serialization of the version of the object) we get a runtime exception.
> The original reason for excluding the '@' symbol was because of URI encoding
> concerns, eg if the OID appeared in a URI for the Restful Objects viewer.
> However, the value would only ever occur in the path part of the URI (if in
> the body or query string, then the RO spec defines base 64 encoding anyway).
> As per http://www.ietf.org/rfc/rfc3986.txt (section 3.3), the path component
> may contain an '@' symbol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
