Hello Rodney,

I can see that you have opened, as I would have suggested, a ticket with Technical Support.

It would seem it is an issue with a Python Library, but let elevate this to Development now and see what they tell us.

Thanks.

Regards,

Luciano Testa

It concerns me this wasn't tested before release.  Every release since 6.4.2 has been a mess for one reason or another.  Please do better QC

Thanks for reporting this, I was in a process of upgrading to 6.4.3.

Can be this fixed ASAP ?

Hello,

Development is working on a fix right now.

6.4.3 has temporarily been removed from the update channel until this is done.

My apologies.

Thanks.

Regards,

Luciano Testa

I upgraded our test system to 6.4.3 no problem with edirectory sync, we use tlsv1.2 and ec certificate

Thank you clausw1  I can confirm that switching edir LDAP to an EC cert, then removing and re-adding that directory server to the AAuth 6.4.3 repository allows communication again. 

We can't switch to EC in near future

Ya, importing the EC root cert into various other products in a large system would be a pain.  I only tested on my home lab with a small number of OES servers and services

Thank-you, but as others have said, this really should have been tested before deployment as this eDirectory use is a very common scenario. I had to revert from a snapshot because of this. It's not good for business continuity.

I see there is a solution for that in knowledge base: https://portal.microfocus.com/s/article/KM000029147

But 6.4.3 still seems to be withdrawn from the channels - is there a time frame for when it will be back?

We are looking forward for an update that hopefully will solve the problems introduced with 6.4.2.

Best regards,

Mirko Guldner