The eThe core UH LDAP servers are ldap.hawaii.edu (recommended) and ldap1.its.hawaii.edu (legacy, slated for retirement) and are based on the uhEduPerson schema.
...
| LDAP Generation | host | port | comments |
|---|---|---|---|
 Next Generation LDAP, Production | ldap.hawaii.edu | 636 for LDAPS, 389 if using startTLS | cleartext or anonymous binds are rejected, a Special DN is required |
| Next Generation LDAP, Test | ldap-test.its.hawaii.edu | 636 for LDAPS, 389 if using startTLS | cleartext or anonymous binds are rejected, a Special DN is required |
 Legacy, Slated for Retirement | ldap1.its.hawaii.edu | 389 | data goes over cleartext, do not provide any passwords when you connect |
| Legacy, Slated for Retirement | ldap1.its.hawaii.edu | 636 | LDAPS, encrypted, always use this when providing a password |
- Connecting to LDAP is referred to as binding.
- You cannot bind to LDAP anonymously, credentials are required for the Next Generation LDAP.
- You must request a special DN in order to bind per UH Data Governance policies.
- Special DNs are only granted when CAS (the Web Login Service) will not suffice.
- Special DN requests are subject to E2.215 and may require a Data Governance approval.
...
You should also look into CAS (the Web Login Service) as an alternative to using LDAP for authentication.