<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
No, connector does not have an option to ignore specific
attributes. However the errors may not be critical. If you are
using AD, 389ds or a similar LDAP server that does not completely
complies with RFCs then you will see the schema errors in the log.
If these are the errors produced by the Apache Directory API then
they are mostly safe to ignore (org.apache.directory package). The
errors produced by the connector code are important
(com.evolveum.polygon.ldap package).<br>
<br>
There are two reasons for that. Firstly there are broken LDAP
servers that just won't comply with the standards. This is the
real reason for the errors, but realistically there is nothing we
can do about this. The secondly, the error handling and reporting
in the Apache Directory API is not ideal. I have made some
improvements in the current version of the Apache Directory API
(as did other contributors). Now there is a possibility for the
connector to process the errors, but the API logs the errors
anyway. The Apache Directory API needs a larger re-engineering of
the error handling code. But that would break API compatibility.
So we (Apache Directory API comitters) have agreed to postpone
these fixes after API 1.0 release. Currently the 1.0-RC2 release
is in progress, therefore we will hopefully get to fixing this
issue soon ...<br>
<br>
If you see any errors from the connector itself I would really
wonder what these are. I have tested the connector with OpenLDAP
(several versions), OpenDJ and 389ds. Almost the same code also
applies to AD and eDirectory operations. Even though there are
some schema errors all the attributes that I have tried worked
fine.<br>
<br>
<pre class="moz-signature" cols="72">--
Radovan Semancik
Software Architect
evolveum.com
</pre>
<br>
<br>
On 10/27/2016 08:38 AM, Brad Fardig wrote:<br>
</div>
<blockquote
cite="mid:SG2PR06MB08707E66855159065F891090CDAA0@SG2PR06MB0870.apcprd06.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is it possible to have the LDAP connector
ignore particular attributes when it is dynamically building
the schema?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have midPoint 3.4 with the LDAP connector
version 1.4.2.19<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am getting errors when the schema is
being retrieved. If I turn quirks mode on the errors are as
shown in connector-error1.log and connector-error2.log (taken
from idm.log. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With quirks mode off the error is shown in
err.txt. The attribute in question here has a complex syntax
that is defined in the schema but doesn’t appear to be
returned by the directory as my LDAP admin tool doesn’t show
the syntax either. The attribute is not used within any
entries in the directory but is defined as a “may” attribute
within several aux object classes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kind Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Brad<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>