I did two things that were significantly different from the multi-site instructions. So far they are working on my local installation, but have not yet been tested in online sites.

This was done in Drupal 7 running under XAMPP 5.6.3.

If you need to import a table of data from an Access database for use in Drupal, you don't need a module to do that. You can use tools provided by Microsoft and Oracle (i.e., MySQL) for connecting the databases. This looks to me like a better way to go than using a Drupal module because it uses a direct data connection between Access and MySQL with nothing intervening that could introduce a potential for error. But I'm open to being corrected on that if others explain why a certain module is a better way to do this.

On this page:

• Goal
• Skills needed
• Detailed steps
• Background and reference information
• Next steps: moving beyond this task

To get help completing this task, see the Getting help completing your task page.

Automatic role population from simpleSAMLphp attributes is achieved by using the following evaluation syntax in admin/config/people/simplesamlphp_auth:

roleid1:condition1|roleid2:contition2

Where roleid is the Drupal role id. The condition determines what value from simpleSAMLphp attributes will be used to determine the role population. The rules are separated with a pipe. Here's an full example:

This Noob guide describes the use of the module Path Breadcrumbs. The terms, options and setup process are described through a simple example.

The following code illustrates how to map IdP attributes to user object fields.

The global variable $_simplesamlphp_auth_saml_attributes defined in simpleSAMLphp_auth contains the attributes passed from the IdP.

This technique can be expanded to do other things related to defining and manipulating the user object during authentication. For instance an associative array is defined to convert the Salesforce account record subtype string to a Drupal role numeric ID.