1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 3<html> 4 <head> 5 <meta name="generator" content="HTML Tidy, see www.w3.org"> 6 <title>User Identification</title> 7 <meta name="GENERATOR" content= 8 "Modular DocBook HTML Stylesheet Version 1.7"> 9 <link rel="HOME" title=" LPRng Reference Manual" href= 10 "index.htm"> 11 <link rel="UP" title="Permissions and Authentication " href= 12 "permsref.htm"> 13 <link rel="PREVIOUS" title="Authentication " href= 14 "authref.htm"> 15 <link rel="NEXT" title="RFC1179 Protocol Extensions" href= 16 "x8980.htm"> 17 </head> 18 19 <body class="SECT1" bgcolor="#FFFFFF" text="#000000" link= 20 "#0000FF" vlink="#840084" alink="#0000FF"> 21 <div class="NAVHEADER"> 22 <table summary="Header navigation table" width="100%" border= 23 "0" cellpadding="0" cellspacing="0"> 24 <tr> 25 <th colspan="3" align="center">LPRng Reference Manual: 5 26 Sep 2003 (For LPRng-3.8.22)</th> 27 </tr> 28 29 <tr> 30 <td width="10%" align="left" valign="bottom"><a href= 31 "authref.htm" accesskey="P">Prev</a></td> 32 33 <td width="80%" align="center" valign="bottom">Chapter 34 17. Permissions and Authentication</td> 35 36 <td width="10%" align="right" valign="bottom"><a href= 37 "x8980.htm" accesskey="N">Next</a></td> 38 </tr> 39 </table> 40 <hr align="LEFT" width="100%"> 41 </div> 42 43 <div class="SECT1"> 44 <h1 class="SECT1"><a name="AEN8974">17.8. User 45 Identification</a></h1> 46 47 <p>When a user logs into a system, they are assigned a user 48 name and a corresponding UserID. This user name is used by 49 the <b class="APPLICATION">LPRng</b> software when 50 transferring jobs to identify the user.</p> 51 52 <p>When we look into the problem of authentication, we will 53 possibly have a more global user identification to deal with, 54 the authentication identifier (AuthID). One way to deal with 55 this problem is to give <b class="APPLICATION">LPRng</b> 56 intimate knowledge of the UserID and AuthID relationship. 57 While this is possible it is difficult to deal with in a 58 simple and extensible manner. An alternate solution is to 59 provide a mapping service, where the authentication procedure 60 provides a map between the UserID and AuthID.</p> 61 </div> 62 63 <div class="NAVFOOTER"> 64 <hr align="LEFT" width="100%"> 65 66 <table summary="Footer navigation table" width="100%" border= 67 "0" cellpadding="0" cellspacing="0"> 68 <tr> 69 <td width="33%" align="left" valign="top"><a href= 70 "authref.htm" accesskey="P">Prev</a></td> 71 72 <td width="34%" align="center" valign="top"><a href= 73 "index.htm" accesskey="H">Home</a></td> 74 75 <td width="33%" align="right" valign="top"><a href= 76 "x8980.htm" accesskey="N">Next</a></td> 77 </tr> 78 79 <tr> 80 <td width="33%" align="left" valign="top"> 81 Authentication</td> 82 83 <td width="34%" align="center" valign="top"><a href= 84 "permsref.htm" accesskey="U">Up</a></td> 85 86 <td width="33%" align="right" valign="top">RFC1179 87 Protocol Extensions</td> 88 </tr> 89 </table> 90 </div> 91 </body> 92</html> 93 94