@techreport{ietf-acap-authid-03,
    number =    {draft-ietf-acap-authid-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-acap-authid/03/},
    author =    {Steve Hole and Alexey Melnikov},
    title =     {{ACAP Authorization Identifier Datasets Classes}},
    pagetotal = 16,
    year =      2002,
    month =     jun,
    day =       16,
    abstract =  {Most distributed (client/server) applications require an authenti- cation process between the client and the server before the server will grant access to its managed resources. Many applications pro- vide varying levels of access to server resources based on a combi- nation of authentication credentials and access control rules. The collection of information used to control access to resources is called 'authorization information'. The authorization identifer datasets contain lists of users and groups of users that can be used by applications for authorization purposes. Access control mechanisms can be abstracted from under- lying authentication mechanisms and credential formats. They can be extended to include group memberships in dynamic calculations for access rights to resources or in definition of one time autho- rization certificates. The Application Configuration Access Protocol (ACAP) supports the remote storage and access of many types of structured configuration information. The authorization identifier datasets specification describes the 'userid' and 'groupid' datasets which contain the authorization information. It also describes ACAP server capabili- ties that advertise a server's support for authorization user and group semantics.},
}