You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
KIM Integration Model |
Pros |
Cons |
#1 (Internal DB) |
- Out of box implementation
- No custom KIM service implementation
|
- No IDM integration
- Must re-enter all person identity manually
- Must manually keep identity data synchronized
|
#2 (Data feed) |
- Authoritative IDM source data is utilized
- No custom KIM service implementation
|
- Must create a synchronization/push process
- Delay is source data propagation
*
|
#3 (Service - LDAP backed) |
- Real-time data currency
- Authoritative IDM source data is utilized
|
- Custom KIM service implementation
- LDAP data source must make all attributes available
- Requires good performing LDAP service
- Introduces external dependency for real-time data access
|
#4 (Service - DB backed) |
- Real-time data currency
- Authoritative IDM source data is utilized
|
- Custom KIM service implementation
- Database data source must make all attributes available
- Requires good performing database service
- Introduces external dependency for real-time data access
|
Institution Implementations
Intuition |
Identity |
Group |
Role/Permission/Responsibility |
IU |
#2 (10 minutes) |
#1 & #2 (AD groups) |
N/A |
CSU |
#2 (nightly) |
#1 |
N/A |
Arizona |
#3 |
#1 |
N/A |
SJD |
#3 |
#1 |
N/A |
NPS |
#3 |
#1 |
N/A |
UCD |
#3 |
#1 |
N/A |
UCM |
#4 |
#1 |
N/A |