1. Federation Participant Information

1.1 – The InCommon Participant Operational Practices information below is for:

InCommon Participant organization name – Lafayette College
The information below is accurate as of this date – February 2017

1.2 – Identity Management and/or Privacy information
Additional information about the Participant’s identity management practices and/or privacy policy regarding personal information can be found online at:


1.3 – Contact information

The following person or office can answer questions about the Participant’s identity management system or resource access management policy or practice.

  • Name: Janemarie Duh
  • Title: Identity Management Systems Architect
  • Email address: duhj@lafayette.edu
  • Phone: 610.330.5609

2. Identity Provider Information

The most critical responsibility that an Identity Provider Participant has to the Federation is to provide trustworthy and accurate identity assertions. It is important for a Resource Provider to know how your electronic identity credentials are issued and how reliable the information associated with a given credential (or person) is.


2.1 – If you are an Identity Provider, how do you define the set of people who are eligible to receive an electronic identity? If exceptions to this definition are allowed, who must approve such an exception?

Our account creation policies are available at http://its.lafayette.edu/policies/accounts

2.2 – “Member of Community” is an assertion that might be offered to enable access to resources made available to individuals who participate in the primary mission of the university or organization. For example, this assertion might apply to anyone whose affiliation is “current student, faculty, or staff.” What subset of persons registered in your identity management system would you identify as a “Member of Community” in Shibboleth identity assertions to other InCommon Participants?

In addition to students, employees, and trustees, we may issue credentials to other individuals who have an affiliation with the College.

Electronic Identity Credentials

2.3 – Please describe in general terms the administrative process used to establish an electronic identity that results in a record for that person being created in your electronic identity database? Please identify the office(s) of record for this purpose. For example, “Registrar’s Office for students; HR for faculty and staff.”

Our policy for account creation is available at: http://its.lafayette.edu/policies/accounts

2.4 – What technologies are used for your electronic identity credentials (e.g., Kerberos, userID/password, PKI, …) that are relevant to Federation activities? If more than one type of electronic credential is issued, how is it determined who receives which type? If multiple credentials are linked, how is this managed (e.g., anyone with a Kerberos credential also can acquire a PKI credential) and recorded?

UserID/Password in LDAP

2.5 – If your electronic identity credentials require the use of a secret password or PIN, and there are circumstances in which that secret would be transmitted across a network without being protected by encryption (i.e., “clear text passwords” are used when accessing campus services), please identify who in your organization can discuss with any other Participant concerns that this might raise for them:

There are no resources that use the Lafayette NetID in an unencrypted way.

2.6 – If you support a “single sign-on” (SSO) or similar campus-wide system to allow a single user authentication action to serve multiple applications, and you will make use of this to authenticate people for InCommon Service Providers, please describe the key security aspects of your SSO system including whether session timeouts are enforced by the system, whether user-initiated session termination is supported, and how use with “public access sites” is protected.

Shibboleth is used for all InCommon Service Providers. Shibboleth delegates authentication and SSO session timeout to CAS. User-initiated SSO session termination is supported by CAS. Public access sites have default system session timeouts.

2.7 – Are your primary electronic identifiers for people, such as “net ID,” eduPersonPrincipalName, or eduPersonTargetedID considered to be unique for all time to the individual to whom they are assigned? If not, what is your policy for re-assignment and is there a hiatus between such reuse?

Yes, NetIDs are considered to be unique for all time to the individual to whom they are assigned. To review our account retention/removal policy, visit: http://its.lafayette.edu/policies/account_removal

Electronic Identity Database

2.8 – How is information in your electronic identity database acquired and updated? Are specific offices designated by your administration to perform this function? Are individuals allowed to update their own information online?

Identity data are primarily sourced from systems of record for student, faculty, and staff and are maintained by authorized administrative units. Individuals must work with the responsible administrative unit to update their own information. Individuals, though, can update their own recovery addresses. In the case of name changes or data discrepancy, identity managers update information such as email address and NetID in the database.

2.9 – What information in this database is considered “public information” and would be provided to any interested party?

Certain data designated as Directory Information that the College may disclose without the consent of the student is available at http://registrar.lafayette.edu/ferpa/.

Uses of Your Electronic Identity Credential System

2.10 – Please identify typical classes of applications for which your electronic identity credentials are used within your own organization.

Web applications
Network File Storage
Network Access (wired and wireless)

Attribute Assertions

Attributes are the information data elements in an attribute assertion you might make to another Federation participant concerning the identity of a person in your identity management system.

2.11 – Would you consider your attribute assertions to be reliable enough to:

control access to on-line information databases licensed to your organization? – YES
be used to purchase goods or services for your organization? – YES
enable access to personal information such as student loan status? – YES

Privacy Policy

Federation Participants must respect the legal and organizational privacy constraints on attribute information provided by other Participants and use it only for its intended purposes.

2.12 – What restrictions do you place on the use of attribute information that you might provide to other Federation participants?

The College has no restrictions other than those it is bound to abide by as outlined in the Participation Agreement. See section 9. Respect for Identity Information at https://www.incommon.org/docs/policies/participationagreement.pdf.

2.13 – What policies govern the use of attribute information that you might release to other Federation participants? For example, is some information subject to FERPA or HIPAA restrictions?

Yes, some information is covered under FERPA.

3. Service Provider Information

Service Providers are trusted to ask for only the information necessary to make an appropriate access control decision, and to not misuse information provided to them by Identity Providers. Service Providers must describe the basis on which access to resources is managed and their practices with respect to attribute information they receive from other Participants.

3.1 – What attribute information about an individual do you require in order to manage access to resources you make available to other Participants? Describe separately for each resource ProviderID that you have registered.


3.2 – What use do you make of attribute information that you receive in addition to basic access control decisions? For example, do you aggregate session access records or records of specific information accessed based on attribute information, or make attribute information available to partner organizations, etc.?


3.3 – What human and technical controls are in place on access to and use of attribute information that might refer to only one specific person (i.e., personally identifiable information)? For example, is this information encrypted?


3.4 – Describe the human and technical controls that are in place on the management of super-user and other privileged accounts that might have the authority to grant access to personally identifiable information?


3.5 – If personally identifiable information is compromised, what actions do you take to notify potentially affected individuals?


Other Information

4.1 – Technical Standards, Versions and Interoperability
Identify the version of Internet2 Shibboleth code release that you are using or, if not using the standard Shibboleth code, what version(s) of the SAML and SOAP and any other relevant standards you have implemented for this purpose.

Shibboleth Identity Provider 3.2.1

4.2 – Other Considerations
Are there any other considerations or information that you wish to make known to other Federation participants with whom you might interoperate? For example, are there concerns about the use of clear text passwords or responsibilities in case of a security breach involving identity information you may have provided?