Authentication (Secure Pages)

Using Shibboleth, Lightweight Directory Access Protocol (LDAP), and Secure Socket Layers (SSL), it is possible to limit access of your published pages to specific LDAP groups or named UB constituents.

To secure a page using the UBCMS, three steps are required: 

• The page name must end in "-pw".
• You must select "Authentication Required" in the page Properties.
• You must set filters, either by choosing from the 'Allowed' dropdown or by adding values to the 'Additional Users/Group' list (or both).

Access is restricted through an authenticated page whose name must end in “–pw” (e.g. mypage-pw). This will limit access to that particular page (i.e. mypage-pw.html) and its children.  (Also the public URL for your new page will always begin https://.) The actual restrictions are set in page Properties.

Within the UBCMS, all hostnames (subdomains) are certified for secure pages (e.g. WWW.buffalo.edu is a hostname, as is NURSING.buffalo.edu). All secure pages rely on a certificate for that hostname, and for all UBCMS pages, the certificate is managed and paid for centrally by UBit. But if your unit operates its own servers with an independent certificate, your unit would be responsible for purchasing and managing that on your own.

Secure pages appear in your site's navigation and lists/carousels in Author, but on your live site, are hidden unless a user has access to view the pages, has authenticated (logged in to a secure UB system), and the user is within the secure part of your site -- otherwise the pages will essentially be invisible. To make secure pages visible in site navigation or lists/carousels, see the Advanced Section below.

Create the new page. The name of must end in “–pw” (e.g. mypage-pw).

This will limit access to that particular page (i.e. mypage-pw.html) and any of its children. 

Set up your page as desired, then adjust that page's settings in Properties as described in the next section.

1. In the Edit Console, click the Equalizer button, then Open Properties and a new screen will load.
2. Select the Advanced tab, then scroll down and expand the Authenticated Published Pages section. 
3. Check Authentication Required to engage your restriction settings. Once you engage this setting, you must set further filters or no one will be able to view the page.

Limiting by LDAP groups is probably best used in cases where another process is already maintaining those groups, such as Student Accounts, and also when the group is too large or unpredictable to manage yourself in the page Properties.  

Some units already maintain LDAP groups for other purposes that may be of use in identifying your staff or faculty or students, so we encourage you to consult with your department IT staff.

Developers with Unix knowledge can look up LDAP group and its members by connecting to ubunix.buffalo.edu through SSH-Telnet. Run these command line queries:  

• grep keyword /etc/group  where keyword is a UBITName, LDAP group, or a partial string of either. This will check if that group exists, and display UBitnames associated with it where that group is not their primary group..
• grep :groupID: in /etc/passwd which will display the names of anyone where this is their primary group.
  
• groups UBitname to display which groups include the specified person (identified by their UBitname).

Note: UBit may refer to these as 'UBLDAP' groups, to distinguish them from the Active Directory (UBAD/ADFS) groups that are used by systems such as email.

LDAP Groups can be created or adjusted directly by individual offices through the UBIT Help Center.

Once a page is secure, because the visitor is now identified, the following parameters are available from LDAP (with an example of the output for Jerod Sikorskyj):

id                   jjs58
path              /home/users/j/jj/jjs/jjs58
displayName  Jerod J Sikorskyj
givenName    Jerod
familyName   Sikorskyj
phone           645-5195
email            jjs58@buffalo.edu
affiliation     staff
department Enterprise Application Services
title             Application Developer
address        108 Academic Center

To use any of these parameters on an authenticated page, you must use the User Info Loader component, located in the author Sidekick under “Form Components.”

Place the User Info Loader component at the top of the page.

• Click on the “+” sign to add a field (“+”changes to a “-“ sign so it can be removed). 
• To make an LDAP parameter available for inclusion on your page, use this syntax:
                  #<variable>=<LDAP parameter>
                  e.g.        #your_name=displayName
• Anywhere in your page that you put an HTML snippet with a named element (e.g. #your_name), the text of that HTML element will become the value of that LDAP variable. So in the above example, <h3 id="your_name">text_to_be_replaced</h3> will display an H3 heading with the value of displayName when published.  
• To use an LDAP parameter in a form, use this syntax: 
                  input[name=<variable>]=<LDAP parameter>
                  e.g.        input[name=emailAddress]=email
• You would then insert a Form container as usual and add the appropriate input fields. 
• For example, to use an LDAP parameter in a Text Field, set the component values to:
  • Element Name: variable (e.g. Element Name: emailAddress)
  • Title: whatever text you wish
• Each variable must match the value you used in the User Info Loader component for name=<variable>; in this case, emailAddress will automatically pull in their email address.

Make sure to activate all pages to the publisher to test them live.

Here is a sample form that includes the user data drawn from LDAP. Access is limited to anyone with a buffalo.edu account.