A service bind requires that the directory authenticate a directory client (or service), such as Teradata Vantage or the Unity server, if used, before the directory authenticates and/or authorizes a directory user to access the service.
Service binds are sometimes required by site security policy, or when the authentication mechanism specifies use of:
- Directory authorization, when authentication is by a non-LDAP mechanism. See Option 3: Non-LDAP External Authentication with Directory Authorization.
- Identity searches (LDAP mechanism only). See Using Identity Searches.
If you do not configure the LDAP mechanism properties that support service binds, LDAP creates an anonymous bind. See Using Anonymous Binds.
Anonymous binds fail if the directory disallows anonymous binds.