Application Defined Permissions for LDAP
draft-greenblatt-ldap-perms-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Bruce Greenblatt | ||
Last updated | 2001-04-03 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In the current ACL Model draft [2], the kinds of permissions that an LDAP server understands are limited to those defined in clause 4.1.1. Certain LDAP integrated applications need to store their own Application Defined Permissions (ADP) as well. For example, consider an application that allows users to perform several different actions on various types of objects.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)