Trusted network binding using LDAP (lightweight directory access protocol)

• US 6,654,891 B1
• Filed: 10/29/1998
• Issued: 11/25/2003
• Est. Priority Date: 10/29/1998
• Status: Expired due to Term

• Current Assignee: Infoblox Incorporated
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Hamilton, Ian, Anderson, Rod, Borsato, Larry W., Waters, Glenn, Gaudet, Mark
• Primary Examiner(s): HUA, LY
• Application Number:
  US09/182,944
• Time in Patent Office: 1,853 Days
• Field of Search: 713/200, 713/201, 370/352
• US Class Current: 726/6
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5076 Update or notification mechanisms, e.g. DynDNS
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus for providing information between a central database and at least one server. A server manager is coupled between the central database and the at least one server. The server manager communicates configuration information between the central database and the at least one server in a single communication channel.

Claims

1. A network comprising:

a Lightweight Directory Access Protocol (LDAP) directory having at least one client credential value with possible IP addresses;

a binding server coupled to the LDAP directory;

at least one client coupled to the binding server, the at least one client having a client credential with an unauthenticated IP address;

wherein the binding server transmits an LDAP request including at least one client credential with said unauthenticated IP address to the LDAP directory, the binding server authenticating the at least one client if said client credential including said unauthenticated IP address matches the at least one client credential value including possible IP addresses.

2. The network as recited by claim 1, further comprising a server coupled to the binding server and the at least one client, the server to dynamically assign said unauthenticated IP address to the at least one client.

3. The network as recited in claim 1, wherein the client credential comprises a client identification.

4. The network as recited in claim 3 wherein the at least one client transmits the client credential as a registration request to the binding server.

5. The network as recited in claim 1, further comprising a central database to store the at least one client credential, wherein said central database is coupled to said binding server.

6. A method for authenticating at least one client in a network comprising:

dynamically assigning an unauthenticated IP address to the at least one client;

receiving a registration request by the at least one client, the registration request including a client credential with said unauthenticated IP address;

comparing the client credential with said unauthenticated IP address to a stored client credential value in a Lightweight Directory Access Protocol (LDAP) directory; and

authenticating said at least one client if said client credential matches said client credential value.

7. The method as recited in claim 6 further comprising:

storing said client credential in a central database if said client is authenticated.