[midPoint] net.tirasa.connid.bundles.ldap.LdapConnector 1.5.2 and "Activation"

Radovan Semancik radovan.semancik at evolveum.com
Tue Jun 27 10:28:18 CEST 2017


Hi,

So, this might indeed be a bug. Or some kind of strange "interference". 
I have seen before that almost all LDAP servers are twisting the LDAP 
standard in one way or another. It is almost impossible to test all 
connector version against all LDAP sevrers. So, we are doing that 
usually only for those servers that are used by midPoint subscribers. 
And if I cannot reproduce the bug it is very difficult for me to fix it.

But MidPoint project is always open to contributions. You are free to 
diagnose the issue and submit a fix. That would be more than appreciated.

-- 
Radovan Semancik
Software Architect
evolveum.com



On 06/27/2017 08:46 AM, Wojciech Staszewski wrote:
> I downloaded previous version 1.4.3 and this one seems to be ok.
>
> Regards,
> Wojciech Staszewski
>
>
> W dniu 26.06.2017 o 23:42, Wojciech Staszewski pisze:
>> Hmmm...
>>
>> When I use Evolveum connector 1.4.4 everything is OK until I add
>> "memberOf" attribute in Schema Handling, as in example on Evolveum web page:
>>
>> <attribute>
>>                  <ref>ri:memberOf</ref>
>>                  <fetchStrategy>explicit</fetchStrategy>
>> </attribute>
>>
>> In this very moment all other attributes of accounts stored in this
>> resource become invisible.
>>
>> Before:  https://www.skygge.com/midpoint/ldap_before_memberof.png
>> After:  https://www.skygge.com/midpoint/ldap_after_memberof.png
>>
>> ???
>> Reg
>> W dniu 26.06.2017 o 10:26, Wojciech Staszewski pisze:
>>> OK, ok, I got it.
>>>
>>> W dniu 26.06.2017 o 10:23, Radovan Semancik pisze:
>>>> On 06/26/2017 10:03 AM, Wojciech Staszewski wrote:
>>>>> I tried to use this connector but I have trouble with it (some very common attributes was missing).
>>>>> Maybe I'll try to configure my resource from scratch once again using this connector...
>>>> I would strongly recommend to use the new connector. The old JNDI-based connector is a development dead end (as is JNDI itself). The old connector is as good as dead. There will be no new development from our side, the connector is no longer supported and we do not plan any fixes. Our last release of the old connector was more than 2 years ago, so it is also out of the 2-year support period for obsolete components that we usually provide to our subscribers. Getting away from that as soon as
>>>> possible would be a good idea.
>>>>
>>>> The new connector is much better in all aspects.
>>>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>




More information about the midPoint mailing list