*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
This is the preferred method of performing authorization on an application is to either check the NetID or permit against a known authorization list. This ensure that if the application is ever placed into a data area that is not protected by CU WebAuth it will not inadvertently share privileged information (fail closed vs. fail open).
2. Public/Private sites
In some cases you may want to have non-SSL public site and a private SSL protected site that uses the same name. This can be accomplished by following the directions at https://confluence.cornell.edu/x/9QobCg. SPECIAL care should be taken to ensure that content that private content is protected. It is possible to have content that IS protected by CU WebAuth on the SSL portion of a website to NOT be protected on the non-SSL portion of the website. This makes sense for a content management system where you want to have a public portion and restricted administrative function, but can be a DISASTER if you do not do application based authorization. This can be a very tricky configuration and special care should be taken to ensure that it is down properly.
...