7.1 Do you have an enterprise Identity and Access Management roadmap?
|
Yes |
No |
In the process of creating one |
|---|---|---|---|
UBC |
|
|
|
Michigan |
|
|
|
Cornell |
|
|
|
Georgetown |
|
|
|
Ohio State |
|
|
|
UMUC |
|
|
|
UofT |
|
|
|
MIT |
|
|
|
UW-M |
|
|
|
UW |
|
|
|
UC-Irvine |
|
|
|
Colorado |
|
|
|
7.2 When applications invoke services on behalf of a user, are requests represented as coming from the user?
|
This is not a goal |
This is an architecture goal but it is only sometimes implemented |
This is generally implemented for services in the local domain |
This is generally implemented for services in the local domain and in the cloud |
Other |
Ohio |
|
|
|
|
|
UMUC |
|
|
|
|
|
UofT |
|
|
|
|
|
MIT |
|
|
|
|
|
UW-M |
|
|
|
|
|
UW |
|
|
|
|
|
UC-Irvine |
|
|
|
|
|
Colorado |
|
|
|
|
|
7.3 When applications invoke services, how do services authenticate the requests?
|
Locally developed solution for mutual authentication |
An n-tier solution such as Shibboleth ECP or CILogon |
Other |
|---|---|---|---|
UMUC |
|
|
WS-Security via SAML assertions |
UofT |
|
|
|
MIT |
|
|
|
UW-M |
|
|
|
UW |
|
|
|
UC-Irvine |
|
|
|
Colorado |
|
|
|
7.4 After requests are authenticated, do services access another service to determine what the requestor is authorized to do?
|
This is not a goal |
This is an architecture goal but it is only sometimes implemented |
This is consistently implemented for services in the local domain |
This is consistently implemented for services in the local domain and in the cloud |
Other |
|---|---|---|---|---|---|
UMUC |
|
|
|
|
|
UofT |
|
|
|
|
|
MIT |
|
|
|
|
|
UW-M |
|
|
|
|
|
UW |
|
|
|
|
|
UC-Irvine |
|
|
|
|
|
Colorado |
|
|
|
|
|
7.5 More generally, how do you manage trust between distributed components ?
Overview
Content Tools