Welcome to UCS@school ID Connector’s documentation!¶
The ID Connector connects an UCS@school directory to any number of other UCS@school directories (1:n). It is designed to connect state directories with school districts, but can also be used in other contexts. The connection takes place unidirectional: user data (user, school affiliation, class affiliations) is transferred from a central directory (e.g. country directory) to district or school directories. Prerequisite is the use of the UCS@school Kelvin API on the school authorities. For this a configuration is necessary in advance to create an assignment “Which school users should be transferred to which remote instance?” Then these users are created, updated and deleted.
In this documentation, you will learn how to administer an ID Connector setup, and we hope to teach you how to develop plugins for ID Connector as well.
At the moment, the ID Connector setup is only used in German-speaking countries. Hence, you will encounter a few German terms in this documentation.
An easy one to guess - it actually refers to the sending side of the sync process, which in Germany most likely is a state department.
This is the organization managing schools. In the ID Connector context it can be thought of as the recipient of sync data.
You can use the clipboard icon on the top right of code examples to easily copy the code without python and bash prompts:
$ echo "hello world"
(Hover with your mouse over the code to see the icon)
- 1. Administration
- 1.1. Admin overview
- 1.2. Admin prerequisites
- 1.3. Installation
- 1.4. Configuration
- 1.5. Trying it out
- 1.6. Starting / Stopping services
- 1.7. Updates
- 1.8. Extra: setting up a second school authority
- 2. Development
- 2.1. Dev overview
- 2.2. Dev prerequisites
- 2.3. Interactions and components
- 2.4. Dev setup
- 2.5. Plugin development
- 2.6. Building
- 2.7. Integration tests
- 3. File Locations
- 4. Example json configurations
- 5. Changelog