Knowledge

Directory service

Source 📝

175:
and distribution have distinct meanings in the design and management of a directory service. Replication is used to indicate that the same directory namespace (the same objects) are copied to another directory server for redundancy and throughput reasons; the replicated namespace is governed by the
46:. It is a shared information infrastructure for locating, managing, administering and organizing everyday items and network resources, which can include volumes, folders, files, printers, users, groups, devices, telephone numbers and other objects. A directory service is a critical component of a 480:: Derived from the original University of Michigan LDAP implementation (like Netscape, Red Hat, Fedora and Sun JSDS implementations), it supports all computer architectures (including Unix and Unix derivatives, Linux, Windows, z/OS and a number of embedded-realtime systems). 301:
Developed by Microsoft to provide directory services for Windows machines before the release of the LDAP-based Active Directory in Windows 2000. Windows Vista continues to support NT Domains after relaxing its minimum authentication
176:
same authority. Distribution is used to indicate that multiple directory servers in different namespaces are interconnected to form a distributed directory service; each namespace can be governed by a different authority.
81:(unique identifier) to each of the objects. Directories typically have a set of rules determining how network resources are named and identified, which usually includes a requirement that the identifiers be 109:. Data can be made redundant if it aids performance (e.g. by repeating values through rows in a table instead of relating them to the contents of a different table through a key, which technique is called 89:. When using a directory service, a user does not have to remember the physical address of a network resource; providing a name locates the resource. Some directory services include 149:
for their object ID. Therefore, directory applications try to reuse standard classes and attributes to maximize the benefit of existing directory-server software.
193: 502: 806: 153: 781: 201: 189: 141:, or multiple phone numbers for "work phone"). Attributes and object classes are usually standardized throughout the industry; for example, 146: 730:"ForgeRock has shuttered the open-source community, and no longer allows new development on their platform under a permissive license" 568: 403:
released Red Hat Directory Server, acquired from AOL's Netscape Security Solutions unit, as a commercial product running on top of
801: 428: 200:
for directory services, initially to support the requirements of inter-carrier electronic messaging and network-name lookup. The
137:
Attributes are sometimes multi-valued, allowing multiple naming attributes at one level (such as machine type and serial number
133:- attributes which can be defined for an instance but can be omitted, with the absence similar to NULL in a relational database 393:
and is used for user administration and configuration and software management; previously known as Novell Directory Services.
279:
before it was deprecated for the LDAP-based Open Directory. Support for NetInfo was removed with the release of 10.5 Leopard.
578: 185: 816: 811: 573: 498: 245: 120:
Directory schemas are object classes, attributes, name bindings and knowledge (namespaces) where an object class has:
354:: Directory service, written in Java, supporting LDAP, Kerberos 5 and the Change Password Protocol; LDAPv3 certified 588: 458:'s next-generation unified directory solution. It integrates storage, synchronization, and proxy functionalities. 418: 341: 209: 63: 404: 396: 251: 47: 451: 663: 351: 205: 172: 729: 704: 233: 67: 188:(OSI) initiative for common network standards and multi-vendor interoperability. During the 1980s, the 618: 462: 408: 357: 315: 114: 563: 530: 518: 472: 345: 275:. After its acquisition by Apple, it was released as open source and was the directory service for 106: 455: 422: 224: 59: 777: 773: 593: 526: 501:-based LDAP server and directory client that runs in any operating environment, under license 442: 378: 161: 82: 66:
by the directory server. Information about a particular resource is stored as a collection of
466: 446: 432: 374: 329: 255: 683: 110: 43: 522: 296: 239: 160:), adding attributes to the must-may list. Directory services are often central to the 90: 164:
design of an IT system and have a correspondingly-fine granularity of access control.
27:
Service that maps the names of network resources to their respective network addresses
795: 766: 583: 547: 138: 94: 17: 483: 369: 283: 510: 377:
implementation of directory services supports multiple architectures, including
289: 86: 55: 361: 62:
which provides such a service. Each resource on the network is considered an
506: 333: 323: 157: 74: 31: 664:"Red Hat Spending $ 23 Million For Ex-Netscape Security Solutions Business" 477: 276: 272: 213: 642: 412: 400: 382: 337: 319: 266: 204:(LDAP) is based on the X.500 directory-information services, using the 551: 517:
Open-source tools to create directory services include OpenLDAP, the
494: 438: 488: 386: 365: 197: 156:
from its parent object class (and ultimately from the root of the
142: 93:
provisions, limiting the availability of directory information to
390: 259: 152:
Object instances are slotted into namespaces; each object class
737: 546:
Name services on Unix systems are typically configured through
708: 145:
attributes and classes are often formally registered with the
619:"When and How You Should Denormalize a Relational Database" 340:, originating from the X.500 directory, created for use in 262:
network environments. It played a role similar to Hesiod.
229:
The first directory service on the Internet, still in use
42:
maps the names of network resources to their respective
550:. Information from name services can be retrieved with 105:
Several things distinguish a directory service from a
425:'s directory service, compatible with LDAP version 3. 77:for the network. The namespace is used to assign a 765: 411:project. Upstream open source project is called 113:; another technique could be the utilization of 348:and supported by successive versions of Windows 8: 318:: Free Open Source server implementation by 271:Developed by NeXT during the late 1980s for 258:' implementation of a directory service for 219:Systems developed before the X.500 include: 533:. Administration is by GOsa or Samba SWAT. 311:LDAP/X.500-based implementations include: 127:- attributes that each instances must have 322:, with commercial support by Red Hat and 70:associated with that resource or object. 610: 469:, replaced the former NT Domain system. 707:. Opends.dev.java.net. Archived from 445:directory service in Java, backed by 202:Lightweight Directory Access Protocol 7: 212:(DAP) string-encoding scheme on the 101:Comparison with relational databases 184:Directory services were part of an 117:for increasing actual throughput). 569:Directory Services Markup Language 525:, which can function as a Windows 25: 807:Computer access control protocols 509:, until 2016, now maintained by 429:Sun Java System Directory Server 238:Based on DNS and used at MIT's 736:. June 1, 2017. Archived from 473:Critical Path Directory Server 73:A directory service defines a 1: 579:LDAP Data Interchange Format 186:Open Systems Interconnection 168:Replication and distribution 574:Hierarchical database model 407:as the community-supported 246:Network Information Service 833: 768:LDAP System Administration 589:Service delivery platform 419:Oracle Internet Directory 336:'s directory service for 210:Directory Access Protocol 452:Oracle Unified Directory 405:Red Hat Enterprise Linux 397:Red Hat Directory Server 389:and several flavours of 364:'s directory server for 48:network operating system 802:Computer access control 764:Carter, Gerald (2003). 529:with Kerberos and LDAP 352:Apache Directory Server 645:. IETF.org. 1978-11-01 465:(NTDS), later renamed 198:X.500 set of standards 686:. Sun.com. 2010-09-07 463:NT Directory Services 344:, first shipped with 18:Directory (databases) 409:389 Directory Server 368:, available through 358:Apple Open Directory 316:389 Directory Server 307:LDAP implementations 564:Access control list 537:Using name services 435:' directory service 375:eDirectory: NetIQ's 346:Windows 2000 Server 107:relational database 817:Domain Name System 812:Directory services 740:on October 3, 2017 456:Oracle Corporation 423:Oracle Corporation 225:Domain Name System 783:978-1-56592-491-8 594:Virtual directory 527:domain controller 519:Kerberos protocol 292:directory service 44:network addresses 36:directory service 16:(Redirected from 824: 787: 771: 750: 749: 747: 745: 726: 720: 719: 717: 716: 701: 695: 694: 692: 691: 684:"Oracle and Sun" 680: 674: 673: 671: 670: 660: 654: 653: 651: 650: 639: 633: 632: 630: 629: 615: 467:Active Directory 447:Sun Microsystems 433:Sun Microsystems 330:Active Directory 256:Sun Microsystems 95:authorized users 52:directory server 21: 832: 831: 827: 826: 825: 823: 822: 821: 792: 791: 790: 784: 763: 759: 754: 753: 743: 741: 728: 727: 723: 714: 712: 703: 702: 698: 689: 687: 682: 681: 677: 668: 666: 662: 661: 657: 648: 646: 641: 640: 636: 627: 625: 617: 616: 612: 607: 602: 560: 544: 539: 505:. Developed by 370:Mac OS X Server 342:Exchange Server 309: 182: 180:Implementations 170: 111:denormalization 103: 28: 23: 22: 15: 12: 11: 5: 830: 828: 820: 819: 814: 809: 804: 794: 793: 789: 788: 782: 774:O'Reilly Media 760: 758: 755: 752: 751: 721: 696: 675: 655: 634: 623:rubygarage.org 609: 608: 606: 603: 601: 598: 597: 596: 591: 586: 581: 576: 571: 566: 559: 556: 543: 540: 538: 535: 523:Samba software 515: 514: 492: 486: 481: 475: 470: 459: 449: 436: 426: 416: 394: 372: 355: 349: 327: 308: 305: 304: 303: 293: 280: 263: 242: 240:Project Athena 230: 181: 178: 169: 166: 135: 134: 128: 102: 99: 91:access control 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 829: 818: 815: 813: 810: 808: 805: 803: 800: 799: 797: 785: 779: 775: 770: 769: 762: 761: 756: 739: 735: 731: 725: 722: 711:on 2007-07-04 710: 706: 700: 697: 685: 679: 676: 665: 659: 656: 644: 638: 635: 624: 620: 614: 611: 604: 599: 595: 592: 590: 587: 585: 584:Metadirectory 582: 580: 577: 575: 572: 570: 567: 565: 562: 561: 557: 555: 553: 549: 548:nsswitch.conf 541: 536: 534: 532: 528: 524: 520: 512: 508: 504: 500: 496: 493: 490: 487: 485: 482: 479: 476: 474: 471: 468: 464: 460: 457: 453: 450: 448: 444: 440: 437: 434: 430: 427: 424: 420: 417: 414: 410: 406: 402: 398: 395: 392: 388: 384: 380: 376: 373: 371: 367: 363: 359: 356: 353: 350: 347: 343: 339: 335: 331: 328: 325: 321: 317: 314: 313: 312: 306: 300: 298: 294: 291: 287: 285: 281: 278: 274: 270: 268: 264: 261: 257: 253: 249: 247: 243: 241: 237: 235: 231: 228: 226: 222: 221: 220: 217: 215: 211: 208:and an X.500 207: 203: 199: 195: 191: 187: 179: 177: 174: 167: 165: 163: 159: 155: 150: 148: 144: 140: 139:concatenation 132: 129: 126: 123: 122: 121: 118: 116: 112: 108: 100: 98: 96: 92: 88: 84: 80: 76: 71: 69: 65: 61: 57: 53: 49: 45: 41: 37: 33: 19: 767: 742:. Retrieved 738:the original 734:timeforafork 733: 724: 713:. Retrieved 709:the original 699: 688:. Retrieved 678: 667:. Retrieved 658: 647:. Retrieved 637: 626:. Retrieved 622: 613: 545: 542:Unix systems 516: 484:Lotus Domino 310: 295: 284:Banyan VINES 282: 265: 252:Yellow Pages 244: 232: 223: 218: 206:TCP/IP stack 196:created the 183: 171: 151: 136: 130: 124: 119: 104: 78: 72: 51: 40:name service 39: 35: 29: 454:: (OUD) is 443:Open-source 421:: (OID) is 250:Originally 173:Replication 87:unambiguous 56:name server 796:Categories 715:2012-01-09 705:"Java.net" 690:2012-01-09 669:2018-04-22 649:2018-02-13 628:2023-04-30 600:References 302:protocols. 297:NT Domains 68:attributes 643:"RFC1034" 605:Citations 531:back ends 513:Community 507:ForgeRock 491:Directory 334:Microsoft 158:hierarchy 75:namespace 32:computing 558:See also 478:OpenLDAP 461:Windows 366:Mac OS X 290:scalable 277:Mac OS X 273:NEXTSTEP 214:Internet 162:security 154:inherits 115:replicas 757:Sources 744:June 1, 413:FreeIPA 401:Red Hat 383:NetWare 379:Windows 338:Windows 320:Red Hat 267:NetInfo 780:  552:getent 511:OpenDJ 495:OpenDJ 439:OpenDS 288:First 248:(NIS): 234:Hesiod 227:(DNS): 83:unique 64:object 60:server 489:Nexor 387:Linux 362:Apple 254:(YP) 143:X.500 58:is a 778:ISBN 746:2017 521:and 503:CDDL 499:Java 497:- a 391:Unix 324:SUSE 260:Unix 192:and 147:IANA 125:Must 85:and 79:name 50:. A 34:, a 194:ISO 190:ITU 131:May 54:or 38:or 30:In 798:: 776:. 772:. 732:. 621:. 554:. 441:: 431:: 399:: 385:, 381:, 360:: 332:: 216:. 97:. 786:. 748:. 718:. 693:. 672:. 652:. 631:. 415:. 326:. 299:: 286:: 269:: 236:: 20:)

Index

Directory (databases)
computing
network addresses
network operating system
name server
server
object
attributes
namespace
unique
unambiguous
access control
authorized users
relational database
denormalization
replicas
concatenation
X.500
IANA
inherits
hierarchy
security
Replication
Open Systems Interconnection
ITU
ISO
X.500 set of standards
Lightweight Directory Access Protocol
TCP/IP stack
Directory Access Protocol

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.