[
https://issues.apache.org/jira/browse/DIRSTUDIO-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804808#comment-16804808
]
Lothar Haeger commented on DIRSTUDIO-1216:
------------------------------------------
Using openldap's ldapsearch for comparison, I get:
{{ldapsearch -h localhost -p 1389 -D "cn=directory manager" -W -b
"cn=SomeRole,cn=OracleDefaultDomain,cn=OracleDBSecurity,cn=Products,cn=OracleContext,dc=example,dc=com"
-s base 'objectClass=*' structuralObjectClass}}
{{version: 1}}
{{#}}
{{# filter: objectClass=*}}
{{# requesting: structuralObjectClass}}
{{#}}
{{# SomeRole,OracleDefaultDomain,OracleDBSecurity,Products,OracleC}}{{
ontext,example,com}}
{{dn:
cn=SomeRole,cn=OracleDefaultDomain,cn=OracleDBSecurity,cn=Pro}}{{ducts,cn=OracleContext,dc=example,dc=com}}
{{structuralObjectClass: orclDBEnterpriseRole_82}}
{{# search result}}
{{# search: 2}}
{{# result: 0 Success}}
{{# numResponses: 2}}
{{# numEntries: 1}}
> Operational attribute "structuralObjectClass" cannot be displayed in entry
> editor if value contains underscore
> --------------------------------------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-1216
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1216
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 2.0.0-M14
> Environment: Studio 2.0.0-M14 with JDK 8u162 on Windows 10, Oracle
> Unified Directory 12c on Linux. The error is independent of JNDI vs Apache
> LDAP API, both configurations show the described error.
> Reporter: Lothar Haeger
> Priority: Minor
> Attachments: entryeditor.png
>
>
> Oracle Unified Directory can be used to integrate with Oracle Database
> security. Role objects have an objectClass "orclDBEnterpriseRole_82", which
> is listed just fine as one of the "objectClass" values.
> The operational attribute "structuralObjectClass" does not display the above
> value, though, but instead reads: ">>> Error, the configured value editor can
> not handle this value! <<<", which I assume is due to the underscore in it's
> value. At least "structuralObjectClass" is displayed properly for other entry
> types like "groupOfUniqueNames" and "inetOrgPerson".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
