Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

Bind error when changing to ldaps in clearpass

This thread has been viewed 2 times
  • 1.  Bind error when changing to ldaps in clearpass

    Posted Sep 04, 2017 10:06 PM

    Hi! we added our active directory certificate to the clearpass trust list but there is a bind error. What are the things that we need to our ad team in order to integrate it using ldaps for more security?



  • 2.  RE: Bind error when changing to ldaps in clearpass

    Posted Sep 04, 2017 10:07 PM

    That's bind error 216 btw



  • 3.  RE: Bind error when changing to ldaps in clearpass

    EMPLOYEE
    Posted Sep 04, 2017 10:09 PM
    Is TCP 636 allowed through to the domain controllers / LDAP servers?


  • 4.  RE: Bind error when changing to ldaps in clearpass

    Posted Sep 04, 2017 10:14 PM

    Hi Tim,

    TCP 636 is allow in all the domain controllers. 



  • 5.  RE: Bind error when changing to ldaps in clearpass

    Posted Sep 04, 2017 10:32 PM

    Yes Tim tcp 636 is allowed. What other possible reasons for that bind error?