...
1: UCSF releases basic attributes (first, last, full and display names, email address, eduPersonPrincipalName, eduPersonAffiliation, eduPersonPrimaryAffiliation and eduPersonScopedAffiliation) for employees and affiliates to all InCommon participants. Only eduPersonPrincipalName, eduPersonAffiliation, eduPersonPrimaryAffiliation and eduPersonScopedAffiliation are released for students. So most integrations should work with no individual configuration. Additional student data releases must be specifically requested from and approved by the appropriate UCSF administrator and are not automatically released.
Requesting Integration with UCTrust
To plan and schedule integration into the UCTrust federation, please contact your campus/site's UCTrust contact so that they can sponsor your request to the UCTrust Work Group.
For services deployed and managed by a third party, please choose one UCTrust campus/site to sponsor your integration request, and work through that UCTrust contact.
Requirements:
The following is required before UCTrust IdP’s will be enabled for a given application/Service:
- Service Provider must be registered with InCommon.
- Service Provider is responsible for providing all user support (i.e., helpdesk) needed for their application.
- Service Provider must have a business relationship with the UCTrust member (i.e., campus/lab) or already be a UCTrust member.
- Service Providers must have a sponsor within UCTrust.
Procedure:
- Service Provider reviews all requirements listed above.
- If all requirements are satisfied, Service Provider submits the UCTrust Service Provider Request Form.
- The UCTrust sponsor identified in the questionnaire receives notification of the submittal and reviews for completeness.
- If complete: UCTrust sponsor adds the Service Provider to the table of applicants/approved providers below and initiates the UCTrust-wide approval process.
- If incomplete: UCTrust sponsor notifies submitter of information needed.
- Service Providers can monitor their application status in the table below.
Service Provider Integration Status
Legend: E: Enabled R (date): Under Review (estimated completion date) I: Application incomplete O: Opt out N: Not applicable C: Consent page enabled
...
...
Service Provider
...
UCTrust Sponsor
...
Submitted
...
UCB
...
UCD
...
UCI
...
UCLA
...
UCM
...
UCOP
...
UCR
...
UCSB
...
UCSC
...
UCSD
...
UCSF
...
LBNL
...
UCLA Spaces (Confluence wiki)
...
UCLA IT Services
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
AYSO
...
UCOP
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
Berkeley Lab Commons
...
LBNL
...
...
E
...
O
...
E
...
E
...
E
...
O
...
E
...
E
...
Connexxus
...
?
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
(original)
...
...
UCOP
...
(update)
...
E
...
E
...
E
...
E
...
Enter Risk Management
...
UCOP
...
E
...
O
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
1
...
ERS (UCOP)
...
?
...
N
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
ERS (UCSD)
...
?
...
N
...
E
...
E
...
1
...
HR LMS
...
UCOP/
SumTotal
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
1
...
Hathitrust
...
?
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
UC Kuali Ready (BCP)
...
?
...
E
...
O
...
E
...
E
...
I
...
O
...
E
...
E
...
E
...
E
...
E
...
UCOP Sharepoint
...
?
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
UCSF Library Wiki
...
UCSF
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
E
...
...
UCOP
...
E
...
E
...
E
...
- x
...
I
...
E
...
E
...
E
...
E
...
1
...
SharePoint Security Token Services
...
UCOP
...
...
E
...
E
...
E
...
E
...
E
...
E
...
...
...
...
E (for employees)
R (for students)
...
...
,
(update)
...
E(new)
...
...
...
1
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Career Center Alumni Services
...
...
...
...
E
...
...
R
(20161111)
...
...
R
(1/31/2017)
...
...
...
E
...
...
...
R
7/13/2017
...
...
...
...
...
...
R(1/9/2018)
...
...
...
...
...
...
...
...
...
...
...
...
1
...
...
...
...
...
E
...
E
...
...
...
...
...
...
Updated request, below
...
...
...
...
E
...
E
...
E
...
...
E
...
E
...
(required by )
...
...
...
...
...
...
...
...
...
...
...
1: UCSF releases basic attributes (first, last, full and display names, email address, eduPersonPrincipalName, eduPersonAffiliation, eduPersonPrimaryAffiliation and eduPersonScopedAffiliation) for employees and affiliates to all InCommon participants. Only eduPersonPrincipalName, eduPersonAffiliation, eduPersonPrimaryAffiliation and eduPersonScopedAffiliation are released for students. So most integrations should work with no individual configuration. Additional student data releases must be specifically requested from and approved by the appropriate UCSF administrator and are not automatically released.