...
Sample Request Flow
IDMS Toolkit
The IDMS Toolkit (IDMSTK is comprised of the following:
- Query Engine
- ARP
- Notifications
- Config
- Change Detector
- System Monitor
- Listener
SP Toolkit
The SP Toolkit (SPTK) is a tool which will allow a local service, Moodle in the example above, to pull in data from multiple sources as if it were only talking to one source. For instance, Moodle can be configured to pull provisioning information from a single LDAP instance, so in this case, the SPTK will allow Moodle to be configured so that it pulls provisioning data from LDAP, but that LDAP is actually the SPTK, and the SPTK in turn pulls in provisioning information from each UC's IdPTK.
) is a program which accepts requests from the various SPTKs (see SPTK section below) for the purposes of account provisioning in a service provider. There is only one IDMSTK per institution, where there could be n SPTKs. The IDMSTK processes basic requests sent from the various SPTKs, and in turn, looks into the institution's local IDMS to fulfill the request. It is possible that not every institution's IDMS will be able to respond to all of the requests.
The IDMSTK will be able to answer the following types of requestsThe SPTK will allow a local service to query the following information:
- Get all of the changed IDs since the given time:
getChangedSubjects(Time t)
- Get all changes for the given subject since the given time:
getChangesForSubjectSinceTime(SubjectID id, Time t)
- Get current state of the given subject:
getSubject(SubjectID id)
- Get the current state of everyone:
getAll()
Info title Note The second bullet above is not 100% clear to me, as I don't think we can expect an IDMS to be able to relay all changes for a given person from a given point in time. So, if someone can clarify this one, that will be great. - Lucas Rockwell
The IDMSTK is comprised of the following:
- Query Engine
- ARP
- Notifications
- Config
- Change Detector
- System Monitor
- Listener
SP Toolkit
The SP Toolkit (SPTK) is a tool which will allow a local service, Moodle in the example above, to pull in data from multiple sources as if it were only talking to one source. For instance, Moodle can be configured to pull provisioning information from a single LDAP instance, so in this case, the SPTK will allow Moodle to be configured so that it pulls provisioning data from LDAP, but that LDAP is actually the SPTK, and the SPTK in turn pulls in provisioning information from each UC's IdPTK.
See the IDMSTK section above for a list of the types of request that the SPTK should be able to handle from the service provider.
The SPTK is comprised of the following:
...