|
|
.net components for .net developers
|
|
|
|
|
|
Home | .NET News |
.NET Resources |
Team Blog |
Publishers |
Advertise with Us |
Feedback
|
|
Browse by
|
|
Product Type
|
|
|
|
|
|
|
|
|
|
Component Type
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Component Class
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.NET CSharp LDAP Library
|
|
Screenshots
|
|
|
Publisher:
Novell
Online Demo
Download Link
|
.NET C# LDAP library provides easy access to any LDAP compliant directory from managed code.
More...
|
|
Pricing
|
|
|
|
|
|
|
|
Product Info
|
Product Class
Business Components
|
Architecture Of Product
32Bit
|
Product Type
Component
|
Built Using
Visual C#.NET
|
ComponentType
.NET Class
100% Managed Code
|
Compatible Containers
.NET Common Language Runtime V1.1
.NET Common Language Runtime V2.0
|
|
|
|
|
|
|
Detailed Description
|
.NET C# LDAP library provides easy access to any LDAP compliant directory from managed code. The library enables the developers to write LDAP enabled applications that access, manage, and update information stored in Novell eDirectory or other LDAP-aware directories. We assume that the user of the library is familiar with general understanding of LDAP before using the class provided in the library. This document provides an overview of the .NET C# LDAP library and programming code examples.
Lightweight Directory Access Protocol (LDAP) is described in RFC 2251-2256 and RFC 2829-2830. It defines a lightweight access mechanism in which clients send requests to and receive responses from LDAP servers.
The LDAP information model comes from X.500 and is based on the entry, which contains information about some object (for example, a person). Entries are composed of attributes, which have a type and one or more values. Each attribute has a syntax that determines what kinds of values are allowed in the attribute (for example, ASCII characters, a jpeg photograph, etc.) and how those values behave during directory operations (for example, is case significant during comparisons).
Entries may be organized in a tree structure, usually based on political, geographical, and organizational boundaries. Other structures are possible, including a flat namespace. Each entry is uniquely named relative to its sibling entries by its relative distinguished name (RDN) consisting of one or more distinguished attribute values from the entry. At the most, one value from each attribute may be used in the RDN. For example, the entry for the person "James Smith" might be named with the "Jonathan Smith" value from the CN (commonName) attribute.
A globally unique name for an entry, called a distinguished name or DN, is constructed by concatenating the sequence of RDNs from the entry up to the root of the tree. For example, if James worked for the Novell Inc, the DN of his Novell entry might be "cn= Jonathan smith,o=Novell,c=US". The DN format used by LDAP is defined in RFC2253.
Operations are provided to authenticate, search and retrieve information, modify, add and delete entries from the tree. An LDAP server may return referrals if it cannot completely service a request (for example if the request specifies a directory base outside of the tree managed by the server). The .NET C# LDAP library offers a programmer the following three options:
-- catch the referrals as exceptions and explicitly issue new requests to the referred-to servers
-- provide an object to establish a new connection to a referred-to server
-- let the library automatically follow the referrals
|
|
|
|
|
|
|
|
Product Spotlight
|
Hosting Spotlight
|
|
|
|
|
|
There are no Reviews for this Product. Be the first to let
the .NET community know about your experience with
.NET CSharp LDAP Library:
- What are the best features of this product?
- Is the product easy to use?
- How is the technical support?
- Have you encountered any problems, bugs with this product?
- What you would like to be changed or added in the future versions?
- Would you recommend this product to other developers?
|
|
|
|
|
|
|
|
|
|
|
|
|