basic-ncsa
Applicable in AuthTrans-class directives.
The basic-ncsa function verifies authorization information sent by the client against a database. The Authorization header is sent as part of the basic server authorization scheme.
This function is usually used in conjunction with the PathCheck-class function require-auth.
Parameters
The following table describes parameters for the basic-ncsa function.
Table 5–27 basic-ncsa parameters|
Parameter |
Description |
|---|---|
|
Specifies the type of authorization to be used. This should always be basic. |
|
|
(Optional) Specifies the full path and base file name of the user database in the server’s native format. The native format is a system DBM file, which is a hashed file format allowing instantaneous access to billions of users. If you use this parameter, don’t use the userfile parameter as well. |
|
|
(Optional) Specifies the full path name of the user database in the NCSA-style HTTPD user file format. This format consists of lines using the format name:password, where password is encrypted. If you use this parameter, don’t use dbm. |
|
|
(Optional) Specifies the NCSA-style HTTPD group file to be used. Each line of a group file consists of group:user1 user2. userN where each user is separated by spaces. |
|
|
bucket |
(Optional) Common to all obj.conf functions. |
Examples
AuthTrans fn=basic-ncsa auth-type=basic dbm=/sun/proxyserver40/userdb/rsPathCheck fn=require-auth auth-type=basic realm="Marketing Plans"AuthTrans fn=basic-ncsa auth-type=basic userfile=/sun/proxyserver40/.htpasswd grpfile=/sun/proxyserver40/.grpfilePathCheck fn=require-auth auth-type=basic realm="Marketing Plans" |
See Also
- © 2010, Oracle Corporation and/or its affiliates