The Experts below are selected from a list of 1683 Experts worldwide ranked by ideXlab platform
Kurt D Zeilenga - One of the best experts on this subject based on the ideXlab platform.
-
the lightweight Directory Access Protocol ldap don t use copy control
RFC, 2011Co-Authors: Kurt D ZeilengaAbstract:This document defines the Lightweight Directory Access Protocol (LDAP) Don't Use Copy control extension, which allows a client to specify that copied information should not be used in providing service. This control is based upon the X.511 dontUseCopy service control option. [STANDARDS-TRACK]
-
lightweight Directory Access Protocol ldap transactions
RFC, 2010Co-Authors: Kurt D ZeilengaAbstract:Lightweight Directory Access Protocol (LDAP) update operations, such as Add, Delete, and Modify operations, have atomic, consistency, isolation, durability (ACID) properties. Each of these update operations act upon an entry. It is often desirable to update two or more entries in a single unit of interaction, a transaction. Transactions are necessary to support a number of applications including resource provisioning. This document extends LDAP to support transactions. This document defines an Experimental Protocol for the Internet community.
-
lightweight Directory Access Protocol ldap Directory information models
RFC, 2006Co-Authors: Kurt D ZeilengaAbstract:The Lightweight Directory Access Protocol (LDAP) is an Internet Protocol for Accessing distributed Directory services that act in accordance with X.500 data and service models. This document describes the X.500 Directory Information Models, as used in LDAP. [STANDARDS- TRACK]
-
lightweight Directory Access Protocol ldap string representation of distinguished names
RFC, 2006Co-Authors: Kurt D ZeilengaAbstract:The X.500 Directory uses distinguished names as the primary keys to entries in the Directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory Protocols. In the Lightweight Directory Access Protocol, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
-
lightweight Directory Access Protocol ldap schema definitions for x 509 certificates
RFC, 2006Co-Authors: Kurt D ZeilengaAbstract:This document describes schema for representing X.509 certificates, X.521 security information, and related elements in directories Accessible using the Lightweight Directory Access Protocol (LDAP). The LDAP definitions for these X.509 and X.521 schema elements replace those provided in RFCs 2252 and 2256. [STANDARDS-TRACK]
T Howes - One of the best experts on this subject based on the ideXlab platform.
-
lightweight Directory Access Protocol ldap string representation of search filters
RFC, 2006Co-Authors: Mark Smith, T HowesAbstract:Lightweight Directory Access Protocol (LDAP) search filters are transmitted in the LDAP Protocol using a binary representation that is appropriate for use on the network. This document defines a human- readable string representation of LDAP search filters that is appropriate for use in LDAP URLs (RFC 4516) and in other applications. [STANDARDS-TRACK]
-
lightweight Directory Access Protocol ldap uniform resource locator
RFC, 2006Co-Authors: Mark Smith, T HowesAbstract:This document describes a format for a Lightweight Directory Access Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL describes an LDAP search operation that is used to retrieve information from an LDAP Directory, or, in the context of an LDAP referral or reference, an LDAP URL describes a service where an LDAP operation may be progressed. [STANDARDS-TRACK]
-
lightweight Directory Access Protocol ldap
2006Co-Authors: T HowesAbstract:This document describes a format for a Lightweight Directory Access Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL describes an LDAP search operation that is used to retrieve information from an LDAP Directory, or, in the context of an LDAP referral or reference, an LDAP URL describes a service where an LDAP operation may be progressed.
-
internet x 509 public key infrastructure operational Protocols ldapv2
RFC, 1999Co-Authors: S Boeyen, T Howes, P RichardAbstract:The Protocol described in this document is designed to satisfy some of the operational requirements within the Internet X.509 Public Key Infrastructure (IPKI). Specifically, this document addresses requirements to provide Access to Public Key Infrastructure (PKI) repositories for the purposes of retrieving PKI information and managing that same information. The mechanism described in this document is based on the Lightweight Directory Access Protocol (LDAP) v2, defined in RFC 1777, defining a profile of that Protocol for use within the IPKI and updates encodings for certificates and revocation lists from RFC 1778. Additional mechanisms addressing PKIX operational requirements are specified in separate documents.
-
lightweight Directory Access Protocol v3 utf 8 string representation of distinguished names
RFC, 1997Co-Authors: M. Wahl, S Kille, T HowesAbstract:The X.500 Directory uses distinguished names as the primary keys to entries in the Directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory Protocols. In the Lightweight Directory Access Protocol, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
M. Wahl - One of the best experts on this subject based on the ideXlab platform.
-
mime Directory profile for ldap schema
RFC, 2000Co-Authors: M. WahlAbstract:This document defines a multipurpose internet mail extensions (MIME) Directory profile for holding a lightweight Directory Access Protocol (LDAP) schema. It is intended for communication with the Internet schema listing service.
-
lightweight Directory Access Protocol v3 extension for transport layer security
Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security, 2000Co-Authors: Jeff Hodges, R Morgan, M. WahlAbstract:This document defines the "Start Transport Layer Security (TLS) Operation" for LDAP [LDAPv3, TLS]. This operation provides for TLS establishment in an LDAP association and is defined in terms of an LDAP extended request.
-
lightweight Directory Access Protocol v3 extensions for dynamic Directory services
RFC, 1999Co-Authors: Y Yaacovi, M. Wahl, T GenoveseAbstract:This document defines the requirements for dynamic Directory services and specifies the format of request and response extended operations for supporting client-server interoperation in a dynamic directories environment.
-
lightweight Directory Access Protocol v3 utf 8 string representation of distinguished names
RFC, 1997Co-Authors: M. Wahl, S Kille, T HowesAbstract:The X.500 Directory uses distinguished names as the primary keys to entries in the Directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory Protocols. In the Lightweight Directory Access Protocol, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
-
Lightweight Directory Access Protocol (v3)
1997Co-Authors: M. Wahl, T Howes, S KilleAbstract:The Protocol described in this document is designed to provide Access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). This Protocol is specifically targeted at management applications and browser applications that provide read/write interactive Access to directories. When used with a Directory supporting the X.500 Protocols, it is intended to be a complement to the X.500 DAP.
S Kille - One of the best experts on this subject based on the ideXlab platform.
-
lightweight Directory Access Protocol v3 utf 8 string representation of distinguished names
RFC, 1997Co-Authors: M. Wahl, S Kille, T HowesAbstract:The X.500 Directory uses distinguished names as the primary keys to entries in the Directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory Protocols. In the Lightweight Directory Access Protocol, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
-
Lightweight Directory Access Protocol (v3)
1997Co-Authors: M. Wahl, T Howes, S KilleAbstract:The Protocol described in this document is designed to provide Access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). This Protocol is specifically targeted at management applications and browser applications that provide read/write interactive Access to directories. When used with a Directory supporting the X.500 Protocols, it is intended to be a complement to the X.500 DAP.
-
lightweight Directory Access Protocol v3 attribute syntax definitions
RFC, 1997Co-Authors: M. Wahl, T Howes, A Coulbeck, S KilleAbstract:The Lightweight Directory Access Protocol (LDAP) [1] requires that the contents of AttributeValue fields in Protocol elements be octet strings. This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP Protocol. The syntaxes defined in this document are referenced by this and other documents that define attribute types. This document also defines the set of attribute types which LDAP servers should support.
-
the string representation of standard attribute syntaxes
The String Representation of Standard Attribute Syntaxes, 1995Co-Authors: T Howes, S Kille, W Yeong, C RobbinsAbstract:The Lightweight Directory Access Protocol (LDAP) [9] requires that the contents of AttributeValue fields in Protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render X.500 Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3].
-
Lightweight Directory Access Protocol
1995Co-Authors: W Yeong, T Howes, S KilleAbstract:The Protocol described in this document is designed to provide Access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This Protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive Access to the X.500 Directory, and is intended to be a complement to the DAP itself.
Angel Rafael España León - One of the best experts on this subject based on the ideXlab platform.
-
gestion de usuarios con ldap lightweight Directory Access Protocol para el acceso a los servicios tecnologicos y a la informacion en las empresas
Journal of Science and Research: Revista Ciencia e Investigación, 2016Co-Authors: José Teodoro Mejía Viteri, María Isabel Gonzáles Valero, Angel Rafael España LeónAbstract:This research aims to conduct an analysis of management services information and users with LDAP (Lightweight / Simplified Directory Access Protocol), their interaction with other technology services company, allowing it to be Accessed through a single user and password. This study allowed us to collect information through a literature review on the LDAP service and its ability to interact with your user Directory Open source technology services; also with Windows Server and Active Directory service is used by companies for their ease of management and Access resources on Windows clients; is intended to provide an alternative for the implementation of each of the services required by public and private companies with tools free use and Access to services for management and administration can be done by integrating or synchronizing with the Directory LDAP.
-
User Management with LDAP(Light weight Directory Access Protocol)for Access to technology and Information Services in Companies
Universidad Técnica de Babahoyo, 2016Co-Authors: José Teodoro Mejía Viteri, María Isabel Gonzáles Valero, Angel Rafael España LeónAbstract:This research aims to conduct an analysis of management services information and users with LDAP (Lightweight / Simplified Directory Access Protocol), their interaction with other technology services company, allowing it to be Accessed through a single user and password. This study allowed us to collect information through a literature review on the LDAP service and its ability to interact with your user Directory Open source technology services; also with Windows Server and Active Directory service is used by companies for their ease of management and Access resources on Windows clients; is intended to provide an alternative for the implementation of each of the services required by public and private companies with tools free use and Access to services for management and administration can be done by integrating or synchronizing with the Directory LDAP