XYGATE User Authentication Reference Manual

XYGATE
®
User Authentication
™
(XUA) 1.85 Reference Manual
Chapter 12. Configuring the LDAP Interface
XYPRO Technology Corporation 78 Proprietary and Confidential
(Item 15):
Do you want to configure the LDAP interface now <Y> 
Checking syntax ...
XYGATEUA 1.80 (c) 1999-2012 XYPRO Technology Corporation XYPRO Technology \N1
20991231
LDAPPASS CHECKSUM 459520 (\N1.$QA2.XUA.LDAPPASS)
XUA - LDAPPASS warning: LDAP GROUP LD3 not defined in UACONF file, value
ignored
UACONF CHECKSUM 541467491 (\N1.$QA2.XUA.ZZTEMP)
UAACL CHECKSUM 740365426 (\N1.$QA2.XUA.UAACL)
No syntax errors found
Syntax check good.
The previous UACONF has been renamed to UACONF01.
UACONF created with new configuration.
This last prompt (Do you want to configure the LDAP interface now) allows
you to review the summary of your entries.
• If you answer Y, the macro updates the UACONF with all the response values as
displayed and makes a copy of the UACONF file (for example, UACONF01 above).
• If you answer N, the macro quits without making the modifications. The macro
once again checks for any syntax errors before updating the UACONF file.
12.6 LDAP-Related Components
The XUA_LDAP_INSTALL macro (section 12.5) creates the following files in the
XYGATEUA installation subvolume:
LDAPSRV
The LDAPSRV file is the executable for the proxy server process that mediates
communication between XUA and the LDAP server.
At startup the LDAP Proxy determines the number of IP addresses mapped to a given
host name. When the LDAP Proxy receives a “Server Down” notification (81), it will
retry that host name again, with the retry count being that determined above. If upon a
retry the proxy makes a successful connection to the server, that connection will be
used for all future communications.
However, if after all retry attempts have failed with “Server Down”, the proxy will then
return a server down notification to XYGATEUA.
Auto-retry results may vary depending upon the behavior of the local nameserver, the
number of LDAP servers mapped to a specific DNS name, and the number of other
programs on various systems requesting LDAP server connections. Because of these
variables, we cannot guarantee that auto-retry will always succeed, even if there are
multiple servers.