UCTrust Workgroup
Child pages
  • Service Provider Integration with UCTrust

Versions Compared

Old Version 109

changes.mady.by.user user-57bf1

Saved on

compared with

New Version 110

changes.mady.by.user Alex Park

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

  1. Service Provider reviews all requirements listed above.
  2. If all requirements are satisfied, Service Provider submits the UCTrust Service Provider Request Form.
  3. The UCTrust sponsor identified in the questionnaire receives notification of the submittal and reviews for completeness.
    1. If complete: UCTrust sponsor adds the Service Provider to the table of applicants/approved providers below and initiates the UCTrust-wide approval process. 
    2. If incomplete: UCTrust sponsor notifies submitter of information needed.
  4. 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


 

Service Provider

UCTrust Sponsor

Submitted

UCB

UCD

UCI

UCLA

UCM

UCOP

UCR

UCSB

UCSC

UCSD

UCSF

LBNL

HAST

UCLA Spaces (Confluence wiki)

UCLA IT Services

 

E

E

E

E

 

E

E

E

E

E

E

E

 

AYSO

UCOP

 

E

E

E

 

 

 

E

 

 

E

E

 

 

Berkeley Lab Commons

LBNL

3/16/2012

E

 

 

E

E

E

 

 

 

 

E

E

 

Connexxus

?

 

E

E

E

E

 

E

E

E

E

E

E

 

R

Decision Support (UCDSS)

UCOP

8/2/2012

E

E

E

E

 

E

E

E

E

E

E

E

 

Enter Risk Management

?

 

E

 

E

E

 

E

 

E

 

E

1

 

 

ERS (UCOP)

?

 

 

 

E

E

 

E

E

E

E

E

E

 

 

ERS (UCSD)

?

 

 

 

 

 

 

E

 

 

 

E

1

 

 

HR LMS

?

 

E

 

E

E

 

E

E

E

E

E

1

 

 

Hathitrust

?

 

E

E

E

E

 

E

E

E

E

E

E

 

 

Jabbr

UC Davis

8/20/2012

 

E

 

E

 

E

E

 

R

 

R

E

 

UC Kuali Ready (BCP)

?

 

E

 

E

E

 

I

 

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

 

 

UC Online Education (CoLE)

UCOP

 

E

E

E

- x

 

I

E

E

 

 

1

 

 

SharePoint Security Token Services

UCOP

9/12/2012

 

E

 

E

 

E

E

 

 

E

E

 

 
DMPToolUCOP1/7/2013 EEE EE   E  
RIM (Resource Identity Manager)UCLA ATS12/19/2013 E E E    E  
SSBart AMP toolUCSD1/23/2013EEE

E (for employees)

R (for students)

 EEE EEE 
UCLA Cloud StorageUCLA           E  
UC Libraries Digital CollectionUCOP7/15/2013 EE  EE   E1  
Jenzebar Higher ReachUCOP9/30/2013     ER      
CTRL RFP (Request for Proposal)UCLA2/07/2014   E R       
OA Policy HarvesterUCOP3/3/2014nana  nananananana

 

nana
eScholarship Submission Management SystemUCOP3/3/2014nana  nananananana nana

Anchor
revoke1
revoke1
 x: 2/15/2013 - UC Online requested an alternate SP configuration due to the vendor's non-compliance with InCommon certificate requirements. The new SP is bilateral with UCLA. It is no longer a UC Trust SP.

1: UCSF releases basic attributes (name, email, ePPN) for most users to all InCommon participants, so most integrations should work with no individual configuration.