Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Directory Services
cnit 242 exam 1
| Term | Definition |
|---|---|
| what is a directory? | centralized, hierarchical information repository about objects in an IT system |
| what is the purpose of a directory? | It functions to organize and centralize information and objects – Users & groups – Devices – Applications |
| what are directory services? | • Protocols, functions, and APIs that allow access to directory information – DAP, LDAP (lightweight directory access protocol), etc. • The benefit provided by the directory to users |
| Directory functions-centralized authentication | For servers, clients, and external applications • Can be used as the basis for single sign on – Expose multiple authentication methods to third party applications |
| Directory functions-phone book | Enables a phone book of sorts about network users - commonly used by email and other systems |
| Directory functions-granularity of administration (more detailed basically) | • A user can be given admin rights for only a portion of the directory • Greatly increases the options available for assigning administrative control |
| Directory structure | • Provides a single logical view of all network resources • arranged in a "tree" structure -- root - branch - leaf resources distinguished via position -a virtual root or context can be specified -locations typically used in ACLs |
| Directory structure-organization | • typically arranged geographically or functionally -both are good, larger organizations may use both |
| Pruning & grafting | • objects can be easily moved from location to location • items can be moved to new locations int he directory • any item can be moved except the root (Individual users, groups, computers, whole directory sections) |
| Attributes in directory | each location of a directory and each object has attributes (variables/characteristics) |
| Inheritance in directory | • items can inherit attributes based on directory location -- helps ensure consistency across items in a directory location -- items moved loose inherited attributes and gain new ones -- greatly eases admin work if configured properly |
| directory schema | -- defines the attribute types a directory can contain + structure One Root – always assumed, rarely specified. Container objects (can be nested) Attributes Leaf Objects Attributes |
| leaf objects | • any object that cannot contain other objects -- ex: person, computer, printer most directory support alias objects which point to other directory entries |
| leaf object attributes | • attributes describe leaf object and are defined in directory schema ex: printer -- make and model -- duplex -- color or B&W -- paper sizes available |
| directory enabled applications | core applications that rely on directory for info • user logon • vpn authen • digital signature verif and storage • single sign-on verif • team collab • doc publish |
| OUs | containers known as organizational units --can be nested |
| Distinguished names | • names that refer to individual entries --can be absolute or relative -relative DNs are relative to a virtual root (called the context) |
| the context | • virtual root of sorts --configurable by user --allows for shorter and more portable naming approaches as long as consistency is assured |
| absolute DN | includes complete location of item all the way from root /.gm.us.manufacturing.fortwayneassy.maintenance.jdoe |
| relative DN | only lists location from current as set in client relative DN= .maintenance.jdoe context= .gm.us.manufacturing.fortwayneassy |
| directory naming conventions | 4 Layers is typical • c = Country • o = Organization • ou = Organizational Unit • cn = Common Name Naming using LDAP(Lightweight Directory Access Protocol): cn=John Doe, ou=Students, o=CIT, c=WL |
| larger organizations and directories | • Once you have multiple locations with multiple departments, the benefits of a directory can be readily realized |
| smaller organizations and directories | For smaller organizations, a directory is not required • Can be confusing due to the inherent complexity • Most small shops with directories typically use a single location in the directory --a sapling rather than a tree |
Created by:
hallerobin
Popular Computers sets