Implementing Kuali Identity Management at your Institution Jasig Spring 2010 Wednesday, March 10, am
2 Implementing Kuali Identity Management at your Institution Eric Westfall Indiana University Dan Seibert University of California, San Diego
Integrating KIM with other IdM products Implementing Kuali Identity Management at your Institution 3
4 KIM Integration Integration with various Identity Management Systems
5 with Intra-campus Web SSO Federated Access to a Rice application KIM as an Identity Provider (IdP) Using Shibboleth Attributes for KIM authorization
6 with Federated Authentication Shibboleth Login Process
7 with Federated Authentication Protecting a Rice application as a Service Provider (SP) A web server and openssl must be available first Install Shibboleth Configure the web server Override KIM Authentication Service Start the Shibboleth daemon, shibd
8 with KIM as an Identity Provider Prerequisites: SSL certificate, source of SAML Metadata Install Shibboleth IdP Load SAML Metadata Configure KIM as the User Authentication Mechanism
9 with KIM as user Authentication Mechanism Define Login Handler to match AuthenticationService Impl Ex: Remote User for reference AuthenticationServiceImpl Username/Password for LDAP Impl
10 with Authorization Attributes Shibboleth Attributes as KIM Authorization Identify Attribute Sources Define Policies for Attribute Handling, for SPs Define New Business Processes Define New Policies
11 with Federated Authentication
12 with Collaborative development of KIM/Grouper Adaptors Chris Hyzer, University of Pennsylvania Differences between KIM and Grouper How they might work together
13 with Differences between KIM and Grouper
14 with Adapter Overview Custom Implementation of KIM Services using Grouper Client API GroupService GroupUpdateService IdentityService
15 with Installation grouperClient.jar grouperKimConnector.jar grouper.client.properties Override kimGroupService
16 Integrating KIM with LDAP UofA LDAP Integration Approach (UCDavis, SJDC also have implementations) Using CAS to connect to LDAP
17 KIM with LDAP (UofA example) UA netid is used for authentication Identity information is available in UA’s Enterprise Directory Service (EDS) Connect to EDS using Spring LDAP and overriding the KIM IdentityService KIM ParameterService provides map between KIM and LDAP attributes In order to use the KIM GUI’s properly, the UIDocumentService is also overridden
18 Integrating KIM with LDAP Configure CAS to connect to LDAP