<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
  <head>
    <meta name="generator" content="HTML Tidy, see www.w3.org">
    <title>User Identification</title>
    <meta name="GENERATOR" content=
    "Modular DocBook HTML Stylesheet Version 1.7">
    <link rel="HOME" title=" LPRng Reference Manual" href=
    "index.htm">
    <link rel="UP" title="Permissions and Authentication " href=
    "permsref.htm">
    <link rel="PREVIOUS" title="Authentication and Encryption "
    href="authref.htm">
    <link rel="NEXT" title="RFC1179 Protocol Extensions" href=
    "x9043.htm">
  </head>

  <body class="SECT1" bgcolor="#FFFFFF" text="#000000" link=
  "#0000FF" vlink="#840084" alink="#0000FF">
    <div class="NAVHEADER">
      <table summary="Header navigation table" width="100%" border=
      "0" cellpadding="0" cellspacing="0">
        <tr>
          <th colspan="3" align="center">LPRng Reference Manual: 24
          Sep 2004 (For LPRng-3.8.28)</th>
        </tr>

        <tr>
          <td width="10%" align="left" valign="bottom"><a href=
          "authref.htm" accesskey="P">Prev</a></td>

          <td width="80%" align="center" valign="bottom">Chapter
          17. Permissions and Authentication</td>

          <td width="10%" align="right" valign="bottom"><a href=
          "x9043.htm" accesskey="N">Next</a></td>
        </tr>
      </table>
      <hr align="LEFT" width="100%">
    </div>

    <div class="SECT1">
      <h1 class="SECT1"><a name="AEN9037">17.8. User
      Identification</a></h1>

      <p>When a user logs into a system, they are assigned a user
      name and a corresponding UserID. This user name is used by
      the <b class="APPLICATION">LPRng</b> software when
      transferring jobs to identify the user.</p>

      <p>When we look into the problem of authentication, we will
      possibly have a more global user identification to deal with,
      the authentication identifier (AuthID). One way to deal with
      this problem is to give <b class="APPLICATION">LPRng</b>
      intimate knowledge of the UserID and AuthID relationship.
      While this is possible it is difficult to deal with in a
      simple and extensible manner. An alternate solution is to
      provide a mapping service, where the authentication procedure
      provides a map between the UserID and AuthID.</p>
    </div>

    <div class="NAVFOOTER">
      <hr align="LEFT" width="100%">

      <table summary="Footer navigation table" width="100%" border=
      "0" cellpadding="0" cellspacing="0">
        <tr>
          <td width="33%" align="left" valign="top"><a href=
          "authref.htm" accesskey="P">Prev</a></td>

          <td width="34%" align="center" valign="top"><a href=
          "index.htm" accesskey="H">Home</a></td>

          <td width="33%" align="right" valign="top"><a href=
          "x9043.htm" accesskey="N">Next</a></td>
        </tr>

        <tr>
          <td width="33%" align="left" valign="top">Authentication
          and Encryption</td>

          <td width="34%" align="center" valign="top"><a href=
          "permsref.htm" accesskey="U">Up</a></td>

          <td width="33%" align="right" valign="top">RFC1179
          Protocol Extensions</td>
        </tr>
      </table>
    </div>
  </body>
</html>
syntax highlighted by Code2HTML, v. 0.9.1