Restricting Access (Both)

Web Design > Restricting Access (Both)

On the secure server, you may choose to use both access by UNI's and maintain a database of usernames and passwords; in this case, your local database will be checked first, and university network IDs second. In your .htaccess file you should put the line:

AuthKrbUserType
both

.htaccess Examples

AuthType Basic
AuthName "Test CheeseWhiz"
AuthKrbUserType both
AuthKrbUserFile full-path-to-mydbfile-webacl.udb
require user zm4 CUkim CUbob
require group CUregStudent_CCOL_U

For an official site, such as a student group or departmental site, the full-path would be

/www/data/cu/yourgroup/yourfile-webacl.udb

For a personal site, on the other hand, you will have to discover the full-path. At the unix command prompt type

echo ~user

and it will return something like the following

/p/rd/user

so the full path name to your file would be

/p/rd/user/yourfile-webacl.udb

The example above would allow the users Kim and Bob who are from my user database and the user zm4 who is affiliated with Columbia. In addition, it would allow users from Columbia who have the Columbia College Registered Student affiliation (CUregStudent_CCOL_U). There are many Columbia affiliations that you may make use of in this way. Remember that you must provide your users with a way to log out.

« Back to Restricting Access

About Affiliations
Creating a Logout Page