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

Stefan Seelmann commented on DIRSTUDIO-996:
-------------------------------------------

This message is not a fatal error but means that the server doesn't provide a 
schema or the connection user has no permission to read the schema. So the 
server admin has to be asked to allow reading the schema.

Even without the actual server schema it's possible to use Studio and e.g. 
browse and edit if sufficient permission exists, however for unknown attributes 
the wrong value editors may be used.

Added a test to cover this case: 
https://github.com/apache/directory-studio/commit/67b96b482bfcce1bb35c2166d97e4c9cb940c195

> Getting Schema Exception error
> ------------------------------
>
>                 Key: DIRSTUDIO-996
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-996
>             Project: Directory Studio
>          Issue Type: Question
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
>         Environment: Personal system
>            Reporter: Pavan Kumar
>            Priority: Minor
>
> Hi All,
> I use Apache studio to access sunone 6.3 ldaps in our environments. I have 
> given all the details of the servers for connection and test connection also 
> works fine.
> When the connection is opened, I get the below error.
> "
> Error while opening connection
>  - No schema information returned by server, using default schema.
> No schema information returned by server, using default schema.
> "
> Its happening for few ldaps but not all and moreover my collegues in other 
> location have no such issues.. they are able to connect to ldap using ADS.
> Kindly help me.
> Regards,
> Pavan



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to