Beatrix: How to Use Security Groups for NetID and Auth0 Security logins (instructions for stakeholders) Security can be used on YSM sites to restrict access to an entire site or one particular directory, or structure group, of a site.
There are two security options available to use via Beatrix without any required set-up in the Profile System: CAS and YNHH IDs.
Using CAS, the Yale University login system, access can be limited to all NetID's or only certain NetID's, YNHH IDs, a domain, or any combination of those parameters.
Alternatively, you can use the External security option. This allows you to create a login using the individual’s non-Yale email to enter the secured portion of your site by creating a login through Auth-0. See Instructions: External User Security (AUTH-0) .
In either case, be sure to follow the Applying Security to A Structure Group instructions.
The following instructions provide information on how to use apply security to a site or a section of a website.
Table of Contents
Applying Security to an entire site
To restrict an entire site, go to the Website properties and toggle on the button Do you want to secure this site?
Once you turn that on, you will see the options for All Net IDs or All YNHH Ids. If you would like a more restricted list, you can select the Security Groups that you create in the Organization section of Beatrix.
See Beatrix: How to Use Security Groups for NetID and Auth0 Security logins (instructions for stakeholders) for instructions on creating security groups.
Creating a Security Login: Generic Component
Please note this security method is deprecated. While it is still used on PCPC, it should not be applied to any new sites.
To edit the PCPC logins, go either to the Learners or Moderators page and select the page properties. The list of logins is there:
Applying Security to a Structure Group
If your security only applies to a single page or folder, you turn this on by going to the Page Properties of the highest level page in the group. Please note, that subpages in a navigational group cannot have different settings from the parent page. The options are the same as they are for applying security to an entire site.
Please note: Security levels cannot be nested. i.e. a child page cannot have different settings than security at the parent page or site setting.
