University of California, Riverside

InCommon Federation: Participant Operational Practices

Credential Provider Information

The most critical responsibility that a Credential 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 known.


2.1 – If you are a Credential 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?

Applicants, students, faculty, alumni and stuff. Exceptions are allowed and must be approved the organizational Chief Financial Administrative Officer.

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?

Students, Faculty, Staff and Alumni

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 theoffice(s) of record for this purpose. For example, "Registrar's Office for students; HR for faculty and staff."

Faculty and Staff receive an electronic identity based on the Payroll and Personnel System (PPS) from Human Resources, Students and Applicants receive an electronic identity based on information in SIS Plus from the Registrar's Office.

2.4 – What technologies are used for your electronic identity credentials (e.g. Kerberos, userID/password, PKI, ...) that may be used with InCommon actions? 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?

UCR NetID and password are used for authentication

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:

All authentication with applications that use UCR NetID, passwords are encrypted when transferred

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 Resource 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.

Single sign-on sessions time out after 8 hours, user-initiated session termination is allowed (after successful login) at, users are advised to not use SSO available services from public access machines.

2.7 – Are your primary electronic identifiers for people, such as "net ID," eduPerson EPPN, 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?

UCR NetIDs are considered unique for all time

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 on-line?

A feed is generated by Institutional Computing daily (based on UCOP's PPS) and delivered to our Directory system for faculty and staff. A feed is generated daily by Institutional Computing (based on the Registrar's SIS Plus database) and delivered to our Directory system for students and applicants

2.9- What information in this database is considered "public information" and would be provided to any interested party?

Name, phone number, department, email address, and affiliation with campus (except for students who request protection via FERPA).

Your 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.

Calendar, Blackboard, Wireless, Financial applications, Email system

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?
  • be used to purchase goods or services for your organization?
  • enable access to personal information such as student loan status?

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?

Information must not be aggregated or provided to any third party without UCR's permission

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?

Students can opt out to prevent public access to their personal directory information (as per FERPA)

The documents "InCommon: Assertion Reliability" and "InCommon: Attribute Assertion Levels of Assurance" discuss how authentication policies and practices might affect the appropriate use of identity assertions you might make. See

"Member" is one possible value for eduPersonAffiliation as defined in the eduPerson schema. It is intended to include faculty, staff, student, and other persons with a basic set of privileges that go with membership in the university community (e.g., library privileges).

"Member of Community" could be derived from other values in eduPersonAffiliation or assigned explicitly as "Member" in the electronic identity database. See

Please see

More Information 

General Campus Information

University of California, Riverside
900 University Ave.
Riverside, CA 92521
Tel: (951) 827-1012

Department Information

Computing & Communications
Computing & Communications Bldg.

Tel: (951) 827-4741
Fax: (951) 827-4541