[
https://issues.apache.org/jira/browse/DIRSTUDIO-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566543#comment-13566543
]
Brad Thurber commented on DIRSTUDIO-866:
----------------------------------------
Agreed (though i know little of LDAP syntax). Let me know if there is anything
further I can provide on this issue if anything.
On a separate note, the Domino admin suggested I try Softerra - which also
flags them as invalid, but continues to load the connection. Objects show up as
"!COM Error" in Browse tree without children.
Right-click/properties in Softerra shows the issues:
Parsing error: No separator found while decoding the attribute's type/value
pair. Source: AGENCY/IHEATON
Parsing error: Invalid OID syntax of the attribute type Source: */O Position: 0
Character: *[0x2a].
Parsing error: No separator found while decoding the attribute's type/value
pair. Source: IHEATON.
Parsing error: Invalid OID syntax of the attribute type Source: */OU Position:
0 Character: *[0x2a].
etc.
It would be nice if DIRSTUDIO could have the option to do the same thing;
however, I respect the position that it is wrong.
> ERR_04196 while opening connection
> ----------------------------------
>
> Key: DIRSTUDIO-866
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-866
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-apacheds
> Affects Versions: 2.0.0-M3
> Environment: Windows 64 bit client
> Domino 8.5.2FP3 server
> Reporter: Brad Thurber
> Attachments: ERR04196.pcapng
>
>
> Error while opening connection
> - ERR_04196 Unexpected character '/' at position 12. Excpected start of
> attributeType descr.
> org.apache.directory.shared.ldap.model.exception.LdapInvalidDnException:
> ERR_04196 Unexpected character '/' at position 12. Excpected start of
> attributeType descr.
> It may not matter, but this is with the JNDI provider as the normal provider
> can't be used at the moment due to DIRSTUDIO-865
> Will attach Wireshark captures
--
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
