I have been trying to find the setting to confirm that.  

On Nov 2, 2018 7:43 AM, Donny Davis <donny@fortnebula.com> wrote:
Is binding allowed in your 389ds instance?


On Fri, Nov 2, 2018, 8:11 AM Jeremy Tourville <jeremy_tourville@hotmail.com wrote:
The backend is 389 DS, no this is not Govt related.  This will be used as a training platform for my local ISSA chapter.  This is a new 389 DS server.  I followed the instructions at https://www.unixmen.com/install-and-configure-ldap-server-in-centos-7/
The server is "stock" with the exceptions of the settings for startTLS and adding certificates, etc (basically, whatever is needed to integrate with the Ovirt Engine.) 
I am using my Admin account to perform the bind.  What I don't understand is why everything else in the aaa setup script works except the login sequence.  It would seem like my certificates are correct, correct use of the admin DN, etc.  The funny part is I can login to the server using the admin account and password yet the same admin account and password fail when using the aaa setup script.  But, that is why I am using the expert knowledge on the list!  Maybe I have overlooked a simple prerequisite setting needed for setup somewhere?

I'll wait for someone to chime in on possible reasons to get this message:
SEVERE  Authn.Result code is: CREDENTIALS_INVALID
[ ERROR ] Login sequence failed                                               

______________________________________________