http://www.ncsu.edu/it/security/ncsu-ca.html

Taxonomy Access Control Lite (TAC Lite) is a module that we have downloaded from the main Drupal site and provided as part of our standard Drupal kit installation. This module is already installed on your Drupal site, but it remains disabled by default.

Normally, the wraplogin module will automatically create an account for a user as soon as they first login to your website. There are times when you will want to create an accoutn ahead of time. Most likely to assign Roles and/or Permissions for users who will be allowed to develop content for your site. There are a few special features of a WRAP user account that you need to be aware of to create the account properly.

Administrator tasks related to user management.

This has happened on a few of our sites. The site works fine, then one day Drupal does an HTTP request and fails for some reason. It throws the HTTP request fails flag, and absolutely refuses to clear it again after the problem is resolved. This results in aggreation items failing to update, crons not running correctly, and the update checking mechanism starts to throw warnings.

This seems to fix the flag, if you have direct access to the database.

Tips and tricks for when things go wrong with Drupal.

This section if for tasks related to installing Drupal and its module and theme files.

Many of the links here are going to be access restricted, so please login to see what piece may be available to you.

This document will share some of the tricks to setting up an OIT-hosted Drupal installation using the modules that we provide.

WRAP is a web-based authentication mechanism that provides a reliable means of verifying your identity without requiring you to login to each individual, potentially insecure server. When you login to WRAP, your username and password are sent to an SSL-secured server where they are verified. Once verified, you are issued a cookie that contains your userid and connection information that has been encrypted by the WRAP Authentication server.

0. Setup

We have a running IdP that was previously setup to use the UNC Federation for metadata. Our IdP is running the 2.0 version of Shibboleth, on a linux-based (RHEL5) VM server. We have Shib configured to run under Apache Tomcat with all public-facing connections proxied through an Apache Httpd.

Our goal was to add the InCommon federation to be able to run in parallel on the same IdP.