All Drupal sites are CAS enabled. It allows builders, editors, and contributors to authenticate in and edit their content. However, Forced CAS Logins can be added to specific pages in order for non editors to access content on a webpage. Only administrators can add forced logins to a page so a request will need to be made using the Campus Web Solutions form. Administrators can navigate to Configuration -> People -> CAS of their site and update pages in the Forced Login section. 

What does this do? 

If someone tries to access the page via a browser window, they will be directed to the CAS log in page where it will require them to log in with their UCR Net ID and password. This may be bypassed if they have already logged in via CAS. They are now considered authenticated users, though they will have no editing capabilities, nor will they be able to access any of the admin toolbars. However, any individual who accesses the page with their UCR Net ID and password, will automatically be added to the People user list with no role. It is a good idea that editors of the site monitor this list. These lists can be used to see who has accessed the site. If historical records are not necessary, it is a good idea to purge this list of non-role authenticated users periodically. 

Multiple pages (paths) can be added to the forced log in list and there is no limit. However, it would be advantageous if a request were to be made for a specific path, or wildcard. That way, going forward, that path can be used for forced logins without the need to continually request more pages/path be added to the list. 

Example: A request for /internal/* to be added to the list of forced login pages. This will allow any page using /internal/... in the path to automatically be included without the need for additional request.